Skip to main content
VulnerabilityPublished

CVE-2026-128091: mcu-tools mcuboot · Info-leak

Affects mcu-tools mcubootSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 2.0 Low : upgrade to 2.5.0 when convenient.

Data as of 13 Nov 2026, 01:04 UTC

CVSS 3.1 base score
2.0Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (zephyr)CVSS 3.12.0
Patch
Available – fixed in 2.5.0
CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade mcu-tools mcuboot to 2.5.0.

Affected software

ProductAffectedFixed in
mcu-toolsmcubootAffected
  • >=1.3.0 <2.5.0
Fixed in
  • 2.5.0
GitHubmcubootpkg:github/mcubootOther threatsAffected
  • >=1.3.0 <2.5.0
Fixed in
  • 2.5.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fixed version of MCUboot is available in version 2.5.0, which properly wipes the AES key context from memory after use. Users should upgrade to MCUboot 2.5.0 or later to remediate this vulnerability.

Description

CVE-2026-128091 is an information leak vulnerability in MCUboot when built with the TinyCrypt crypto backend. The vulnerability arises because the AES-128 key schedule used for image encryption is not cleared from memory after boot, leaving sensitive key material accessible in RAM. This allows an attacker with physical or code-level access to recover the image content encryption key and decrypt the encrypted image. The device's long-term private keys and image authenticity are not impacted. A fix is available in MCUboot version 2.5.0 that wipes the key context from memory.

References

Community reviews

Loading reviews…