On this page (6 sections)

On 17 November 2026 Ubuntu published USN-9150-1, a security notice for SWUpdate, the update framework used on embedded Linux systems. It fixes two vulnerabilities: a local race condition (CVE-2025-41259) and an improper certificate validation flaw (CVE-2026-109399) that could let an attacker install a malicious update.

If you run devices, gateways or appliances that use SWUpdate to receive firmware or software updates, or you manage Ubuntu 22.04, 24.04 or 26.04 LTS systems with the swupdate package installed, this notice is relevant to you. Most ordinary web servers will not have this package at all, so the first job is to find out whether you do.

What was fixed in USN-9150-1

SWUpdate is described by Ubuntu as a software update framework for embedded systems. The notice bundles fixes for two separate problems, and they differ a lot in who can trigger them.

CVE-2025-41259: a race condition in cleanup

According to Ubuntu, SWUpdate did not verify that a path was a directory before cleaning it up, which created a race condition. A local attacker could possibly use it to escalate privileges or install untrusted content using a signed update. The GitHub advisory describes it as a time-of-check time-of-use (TOCTOU) flaw affecting SWUpdate before 2026.05, rates it High (7.3 on CVSS v4) and lists the attack vector as local with low privileges required. The CVE record maps it to CWE-367. A researcher advisory from SBA Research is referenced, and an upstream fix commit exists.

CVE-2026-109399: untrusted certificates inside signatures

The second flaw sits in certificate handling. Per the GitHub advisory, SWUpdate through 2026.05.1 has an improper certificate validation issue in crypto/swupdate_cms_verify_openssl.c. When building the certificate chain, it trusts X.509 certificates embedded in the CMS SignedData of an update signature. An attacker who holds a signing key from a sibling intermediate CA under the same root can embed that intermediate in the signature and get a malicious update installed.

The advisory scores it Critical at 9.2 on CVSS v4, with a network attack vector, high attack complexity, no privileges and no user interaction required. The high complexity reflects that the attacker needs a signing key from another intermediate under the same root, so this is not an issue for anyone on the internet, but it matters for organizations that run a multi-intermediate PKI. VulnCheck also published an advisory, and an upstream fix commit is referenced.

Ubuntu describes the behavior change plainly: after the update, SWUpdate ignores certificates embedded in CMS signatures. Ubuntu states this second issue only affected Ubuntu 22.04 LTS and 26.04 LTS.

Who is realistically exposed

SWUpdate is firmware and software update tooling, so exposure is concentrated in a few groups:

  • Teams running Ubuntu 22.04, 24.04 or 26.04 LTS with the swupdate package installed.
  • Manufacturers and integrators who build SWUpdate into embedded products such as gateways, controllers and appliances, including those that do not use Ubuntu at all.
  • Organizations that sign updates with a PKI containing several intermediate CAs under one root, because that is the precondition for CVE-2026-109399.
  • Multi-user devices where untrusted local accounts exist, because CVE-2025-41259 needs local access.
The GitHub advisory entries list affected and patched versions as unknown and carry no package mapping. Upstream version ranges come from the CVE descriptions only. For non-Ubuntu builds, check the upstream project and your vendor rather than assuming a version number is safe.

The sources do not say whether either flaw is being exploited, and neither CVE appears in the CISA KEV data provided. Treat that as unknown rather than as a sign of safety, particularly for the critical one.

How to check whether you are affected

On Debian-based systems such as Ubuntu, this read-only command shows whether the swupdate package is installed and which version. No output or a not-installed status means the package is not present.

Check for the swupdate package and version (Ubuntu/Debian)Shell
dpkg -l swupdate

To compare against the fixed versions, this read-only command shows the installed and candidate versions from your configured repositories. Fixes come through Ubuntu Pro (ESM Apps), so the candidate only shows a fixed version if that service is enabled.

Show installed and candidate swupdate versions (Ubuntu/Debian)Shell
apt-cache policy swupdate

Compare the result with the fixed package versions below.

Fixed swupdate package versions from USN-9150-1
Ubuntu releaseFixed versionFix channel
26.04 LTS (resolute)2025.12+dfsg-4ubuntu1+esm1Ubuntu Pro (ESM Apps)
24.04 LTS (noble)2023.12.1+dfsg-1ubuntu5+esm1Ubuntu Pro (ESM Apps)
22.04 LTS (jammy)2021.11-1ubuntu0.1~esm1Ubuntu Pro (ESM Apps)

For embedded products you build yourself, check which SWUpdate release your firmware image bundles and whether signature verification is enabled with CMS and OpenSSL, since the certificate flaw lives in the OpenSSL-based CMS verification file.

What to do now

  1. Inventory every system and device image that includes SWUpdate, including appliances from vendors.
  2. On Ubuntu, confirm whether Ubuntu Pro with ESM Apps is enabled, since the fixes are delivered there. Ubuntu says Pro is free for up to five machines.
  3. Install the updated swupdate package on 22.04, 24.04 and 26.04 LTS systems.
  4. Restart SWUpdate after the update. Ubuntu says this is required to apply all the changes.
  5. For self-built embedded firmware, move to an upstream release that includes the fix commits for both CVEs and ship a new image.
  6. Review your signing PKI: list the intermediate CAs under your root and who holds their signing keys.
  7. Check which local accounts exist on devices running SWUpdate and remove ones that are not needed.

After a standard update, this command upgrades only the swupdate package on Ubuntu or Debian. It needs root privileges and a repository that serves the fixed version.

Upgrade only the swupdate package (Ubuntu/Debian)Shell
sudo apt-get install --only-upgrade swupdate
Caution. Restarting SWUpdate on a device that is in the middle of an update, or that controls production equipment, can interrupt the update or the service. Schedule the restart in a maintenance window and confirm no update is running first. The sources do not name the service unit, so check how SWUpdate is launched on your system.

Detection and monitoring afterwards

A malicious but validly accepted update leaves little obvious trace in the network, so monitoring has to focus on the devices and the signing process.

  • Log and review every update installation: which package or image, which signing certificate, and who initiated it.
  • Alert on updates signed by an unexpected intermediate CA, even if the device accepted them.
  • Keep signing keys for each intermediate separate and tightly controlled, and rotate any you suspect was exposed.
  • Watch for unexpected privilege changes or new files in SWUpdate working directories on shared devices.

If you also run public-facing sites, it is worth keeping certificate and DNS changes under watch, for example with Webforta Monitor and the free SSL checker. Those cover your public endpoints, not the internal signing PKI of a device fleet. For wider patching habits, see our small business website security guide.

Timeline

Dates from the research
DateEvent
3 June 2026CVE-2025-41259 published by NVD and added to the GitHub Advisory Database
12 October 2026CVE-2026-109399 published by NVD and added to the GitHub Advisory Database
17 November 2026Ubuntu publishes USN-9150-1 with fixes for 22.04, 24.04 and 26.04 LTS

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2025-41259 - GitHub Advisory Databasegithub.com
  2. CVE-2026-109399 - GitHub Advisory Databasegithub.com
  3. USN-9150-1: SWUpdate vulnerabilities | Ubuntu security notices | Ubuntuubuntu.com ·
  • SWUpdate
  • Ubuntu
  • USN-9150-1
  • embedded
  • firmware updates
  • CVE-2026-109399