{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-127928 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-127928 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-127928 is a low-severity vulnerability in mcu-tools mcuboot, published on 13 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-127928 and fix it if it is affected.\n\nWhat it is: CVE-2026-127928 is a low-severity vulnerability in mcu-tools mcuboot, published on 13 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-127928 in the wild and no public exploit code.\n\nAffected product: mcu-tools mcuboot. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-127928/ (Markdown: https://insights.sbomify.com/CVE-2026-127928/index.md)","id":"CVE-2026-127928","markdown":"https://insights.sbomify.com/CVE-2026-127928/index.md","name":"CVE-2026-127928","record":{"aliases":["GHSA-hqmg-jwp9-8cf8"],"analysis":null,"analysis_generated_by":null,"assigner":"zephyr","cpe":[],"cvss":{"score":2,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-226","name":"Sensitive Information in Resource Not Removed Before Reuse"}],"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().\n\nThe 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.\n\nThis 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"AES image key left on the stack after serial-recovery encrypted-image handling in MCUboot","id":"CVE-2026-127928","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":2,"n_vendor_status":0,"next":{"headline":"Gitea disclosure of pending pull request reviews created through the API","id":"CVE-2026-127958"},"nickname":null,"packages":[],"prev":{"headline":"AppPresser \u003c= 5.0.0 - Unauthenticated SQL Injection via 'appp_cam_file' Filename Parameter","id":"CVE-2026-127921"},"products":["mcuboot"],"published":"2026-11-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-11-17","vendor_status":[],"vendors":["mcu-tools"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-127928/"}