CVE-2026-127928 AES image key left on the stack after serial-recovery encrypted-image handling in MCUboot

Low 2.0 Published Updated
Exploited in the wild
Not known
Fix
None listed

What is CVE-2026-127928?

CVE-2026-127928 is a low-severity vulnerability in mcu-tools mcuboot, published on 13 Nov 2026.

Official description

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.

Weakness: CWE-226

Which versions are affected by CVE-2026-127928?

How do I fix CVE-2026-127928?

No fix has been published for CVE-2026-127928 yet. Limit exposure of the affected software until one is available.

Is CVE-2026-127928 being exploited?

There is no known exploitation of CVE-2026-127928 in the wild and no public exploit code.

Sources

Also known as GHSA-hqmg-jwp9-8cf8.

Is CVE-2026-127928 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free