CVSS 3.1
2.0 lowCVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:NCVE-2026-128091 AES key schedule not cleared by the TinyCrypt AES-CTR backend in MCUboot bootutil
Low (2.0) in mcu-tools mcuboot. EPSS 0.08% estimated probability of exploitation activity in the next 30 days.
On this page
When MCUboot is built with the TinyCrypt crypto backend (MCUBOOT_USE_TINYCRYPT), bootutil_aes_ctr_drop() in boot/bootutil/include/bootutil/crypto/aes_ctr_tinycrypt.h was an empty stub. The AES-CTR context for this backend is the fully expanded AES-128 key schedule (struct tc_aes_key_sched_struct). Generic code relies on this hook to release and clear key state, so with TinyCrypt nothing was cleared. The mbedTLS and PSA backends do free or destroy their key state here.
As a result, boot_state_clear(), which boot_go() calls before handing off to the application, left the image's AES content-encryption key schedule in the static boot_data state. This is the case after an encrypted upgrade in single-image builds, where boot_enc_zeroize() is not called. boot_decrypt_key() likewise left the ECIES-derived key-encryption key schedule on the stack. The affected build uses MCUBOOT_ENC_IMAGES with TinyCrypt, which is the default ECDSA and Ed25519 backend in the Zephyr port.
The first AES-128 round key equals the cipher key, so anyone who can read the leftover bootloader RAM after boot can recover the image content key and decrypt that encrypted image. That includes a physical attacker with debug or RAM access, or code later running on the device. This weakens image-encryption key confidentiality (and so the confidentiality of the encrypted image's plaintext). The device's long-term private decryption key is not exposed, and image authenticity is not affected. The fix wipes the context with bootutil_wipe_memory().
Severity
- EPSS
- 0.08% estimated probability of exploitation activity in the next 30 days; 0th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-226 Sensitive Information in Resource Not Removed Before Reuse
- Published
- Modified
- Assigned by
- zephyr (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-128091 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-128091?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-128091?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-128091 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-128091)
HTML:
<a href="https://cve.bz/cve/CVE-2026-128091"><img src="https://cve.bz/cve/badge/CVE-2026-128091.svg" alt="CVE-2026-128091"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| mcu-tools mcuboot | from 1.3.0 before 2.5.0 |
Attack patterns (CAPEC)
- CAPEC-37 Retrieve Embedded Sensitive Data Likelihood: High · Severity: Very High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.