Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

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

CVSS 3.1 2.0 LOWCheck source for fixed versionsKEV status unknown

cve-program · CVE-2026-127928

Published

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.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-127928

Published

mcuboot

https://github.com/mcu-tools/mcuboot

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "mcu-tools",
                    "product": "mcuboot",
                    "collectionURL": "https://github.com/mcu-tools/mcuboot",
                    "packageName": "mcuboot",
                    "defaultStatus": "unaffected",
                    "programFiles": [
                        "boot/boot_serial/src/boot_serial_encryption.c",
                        "boot/zephyr/single_loader.c"
                    ],
                    "programRoutines": [
                        {
                            "name": "boot_image_validate_encrypted"
                        },
                        {
                            "name": "decrypt_image_inplace"
                        }
                    ],
                    "versions": [
                        {
                            "version": "1.9.0",
                            "status": "affected",
                            "versionType": "semver",
                            "lessThan": "2.5.0"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 03:41 UTC · 274 of 275 readable · 259 fully read · 11 waiting for GitHub's hourly limit · documentation 469/469 current