CVE-2026-128091
LOWDescription
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().
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 0% of all known CVEs.
References
Related Vulnerabilities
Other CWE-226 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2020-27218 | Medium | 4.8 | 8.3% | - | Fix |
| CVE-2018-7166 | High | 7.5 | 3.3% | - | Fix |
| CVE-2022-39393 | High | 8.6 | 0.9% | - | Fix |
| CVE-2026-92708 | High | 7.5 | 0.7% | - | Fix |
| CVE-2024-32036 | Medium | 5.3 | 0.6% | - | Fix |
| CVE-2026-5795 | High | 7.4 | 0.5% | - | Fix |
Common questions
How do I fix CVE-2026-128091?
No published fix for CVE-2026-128091 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-128091 being actively exploited?
Not that we know of. CVE-2026-128091 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.08% is the estimated probability that it will be exploited in the next 30 days. That is higher than 0% of all scored CVEs.
How severe is CVE-2026-128091?
CVE-2026-128091 has a CVSS v3 base score of 2.0, rated low. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-128091
Markdown
[](https://tridentstack.com/cve/CVE-2026-128091)HTML
<a href="https://tridentstack.com/cve/CVE-2026-128091"><img src="https://tridentstack.com/cve/badge/CVE-2026-128091.svg" alt="CVE-2026-128091"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-11-17.