CVE-2026-127928
Last modified
CVE-2026-127928 is a low-severity vulnerability rated 2/10 on the CVSS scale. 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. EPSS estimates a 0.08% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| mcu-tools | mcuboot | >= 1.9.0, < 2.5.0 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-127928?
How severe is CVE-2026-127928?
How do I fix CVE-2026-127928?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-12787A vulnerability was found in zhilink 智互联(深圳)科技有限公司 ADP Appli…6.3
- CVE-2026-12788A vulnerability was determined in zhilink 智互联(深圳)科技有限公司 ADP …6.3
- CVE-2026-12789A vulnerability was identified in ILIAS Learning Management …4.7
- CVE-2026-1279The Employee Directory plugin for WordPress is vulnerable to…6.4
- CVE-2026-127915The MCUboot TLV iterator bootutil_tlv_iter_next() in boot/bo…2
- CVE-2026-127916bootutil_img_hash() computes the image digest over ih_hdr_si…2.9
- CVE-2026-12793The JetFormBuilder — Dynamic Blocks Form Builder plugin for …9.8
- CVE-2026-12795A vulnerability was determined in BerriAI litellm up to 1.82…7.3
- CVE-2026-12796A vulnerability was identified in BerriAI litellm up to 1.82…6.3
- CVE-2026-12797A security flaw has been discovered in BerriAI litellm up to…6.3
- CVE-2026-12798A weakness has been identified in BerriAI litellm up to 1.82…6.3
- CVE-2026-12799A security vulnerability has been detected in BerriAI litell…4.3
Are you affected by CVE-2026-127928?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
