SWUpdate 2026.05.2 released

20 November 2026

SWUpdate 2026.05.2 is a security release of the 2026.05 stable branch. Please update, in particular if you use signed images with forced-signer-name or the GPG backend.

Security fixes

  • CMS / PKCS#7 signer name check (forced-signer-name): a crafted signature could cause a double free before the signature was verified (GHSA-68fx-rv4m-vh4r).
  • CMS / PKCS#7 signer name check (forced-signer-name): the check could be bypassed by a signer whose certificate chains to the device keyring, adding a certificate or a second signer with the expected name (GHSA-9r86-v62q-p96r).
  • GPG backend with gpgme-protocol = "cms": a signature from any certificate, also a self-signed one, was accepted. The root CA must now be listed in trustlist.txt (GHSA-p837-xh6v-hmff).

Hardening

  • postfailure scripts are not run if they were not extracted and verified
  • wolfSSL PKCS#7: check allocations and fix a memory leak

Other

  • test: fix the expected return value in the hash test

The fixes are also in master and will be part of the next release. On master, SWUpdate now uses /run/swupdate as temporary directory if TMPDIR is not set, and warns at startup if the temporary directory is not private.

The release is tagged on the 2026.05-y branch, and meta-swupdate is updated on all maintained branches.

Sources: tag 2026.05.2 on GitHub · Security advisories