CVE-2026-127928
LOWDescription
In MCUboot's serial-recovery encrypted-image support (boot/boot_serial/src/boot_serial_encryption.c), decrypt_image_inplace() and boot_image_validate_encrypted() each keep a stack-local struct boot_status. boot_enc_load() writes the plaintext per-image AES key into its enckey[] field. Neither function cleared this structure before returning. In addition, a decrypt failure inside the per-sector loop of decrypt_image_inplace() returned early and skipped the total_out: cleanup, which left the expanded AES key context (enc_data) on the stack as well. The error paths of boot_image_validate_encrypted() similarly skipped boot_enc_zeroize(). The affected code is built when encrypted images (MCUBOOT_ENC_IMAGES, Zephyr CONFIG_BOOT_ENCRYPT_IMAGE) are combined with serial recovery. It runs when an encrypted image is uploaded to the primary slot over the recovery protocol, and when the image list or state is queried while an encrypted image is in the secondary slot. After these functions return, the image's AES content key remains in dead stack memory. An attacker who can later read device RAM, for example through a debug port or retained RAM, can recover it. This weakens the confidentiality of image-encryption keys within the bootloader trust boundary. A recovered key exposes the plaintext of the encrypted firmware image it protects. The device's long-term private decryption key is not exposed. No remote or recovery-protocol channel that returns this memory is known, so exploitation requires a separate memory-read capability.
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-127928?
No published fix for CVE-2026-127928 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-127928 being actively exploited?
Not that we know of. CVE-2026-127928 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-127928?
CVE-2026-127928 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-127928
Markdown
[](https://tridentstack.com/cve/CVE-2026-127928)HTML
<a href="https://tridentstack.com/cve/CVE-2026-127928"><img src="https://tridentstack.com/cve/badge/CVE-2026-127928.svg" alt="CVE-2026-127928"></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.