Read the docs

AES image key left on the stack in MCUboot serial recovery

Priority LOW 9CWE-226Published · Updated

Key facts

Attack vector
Physical
Privileges required
None
User interaction
None
Attack complexity
High
Impact type
—
Confidentiality · integrity · availability
Low · None · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA.

Summary

MCUboot versions from 1.9.0 before 2.5.0 leave the plaintext AES image key on the stack after serial-recovery encrypted-image handling. The functions decrypt_image_inplace() and boot_image_validate_encrypted() do not clear their stack structures before returning, and some error paths skip key cleanup. This is CWE-226. An attacker who can read device RAM through a debug port or retained RAM can recover the key and decrypt the protected firmware image, though no remote or recovery-protocol channel that returns this memory is known.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Description from the CNA

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.

Why it matters now

EPSS 0.00083 0th percentileScored 2026-11-16
Fix Fixed mcuboot (mcu-tools): 2.5.0

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
mcu-toolsmcuboot1.9.0 to before 2.5.02.5.0Patch availableCNA
  • mcuboot Vendormcu-tools Affected 1.9.0 to before 2.5.0 Fixed in 2.5.0 Patch available CNA

Remediation

Update mcuboot to 2.5.0, which is the fixed version. The sources list no fixed version for other products.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

  • Fix · CNA mcuboot (mcu-tools) Fixed in 2.5.0

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    mcu-tools mcuboot 2.5.0

    7 records Highest priority Priority LOW 7 LOW

    Other records, highest priority first

    • TI-2026-91071 NULL pointer dereference in MCUboot serial recovery image uploadPriority LOW 17
    • TI-2026-91078 Out-of-bounds read in MCUboot image hash during validationPriority LOW 13
    • TI-2026-91074 MCUboot split-image out-of-bounds stack write with SHA-384/SHA-512Priority LOW 13

Timeline

  1. 2026-11-13 Threatist record created from CVE-2026-127928

References

  • TI-2024-21755 MCUboot Injection attack of unprotected TLV values CVSS 3.1HIGH 7.7
  • TI-2026-91073 Out-of-bounds read in MCUboot serial recovery image index CVSS 3.1MEDIUM 5.1
  • TI-2026-91071 NULL pointer dereference in MCUboot serial recovery image upload CVSS 3.1MEDIUM 4.0
  • TI-2026-91078 Out-of-bounds read in MCUboot image hash during validation CVSS 3.1LOW 2.9
  • TI-2026-91074 MCUboot split-image out-of-bounds stack write with SHA-384/SHA-512 CVSS 3.1LOW 2.9
  • TI-2026-91072 Uninitialised stack memory leaks into MCUboot measured-boot record CVSS 3.1LOW 2.4
See all 8 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences