CVE-2026-128091: fallo de gravedad baja en mcu-tools mcuboot
AES key schedule not cleared by the TinyCrypt AES-CTR backend in MCUboot bootutil
Publicada el · Actualizada el
Aviso por correo cuando entre en el KEV, tenga PoC pública o suba de nota.
8Vexday Risk Score
Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.
ssvc Trackcvss 2epss 0.1%
When MCUboot is built with the TinyCrypt crypto backend (MCUBOOT_USE_TINYCRYPT), bootutil_aes_ctr_drop() in boot/bootutil/include/bootutil/crypto/aes_ctr_tinycrypt.h was an empty stub. The AES-CTR context for this backend is the fully expanded AES-128 key schedule (struct tc_aes_key_sched_struct). Generic code relies on this hook to release and clear key state, so with TinyCrypt nothing was cleared. The mbedTLS and PSA backends do free or destroy their key state here.
As a result, boot_state_clear(), which boot_go() calls before handing off to the application, left the image's AES content-encryption key schedule in the static boot_data state. This is the case after an encrypted upgrade in single-image builds, where boot_enc_zeroize() is not called. boot_decrypt_key() likewise left the ECIES-derived key-encryption key schedule on the stack. The affected build uses MCUBOOT_ENC_IMAGES with TinyCrypt, which is the default ECDSA and Ed25519 backend in the Zephyr port.
The first AES-128 round key equals the cipher key, so anyone who can read the leftover bootloader RAM after boot can recover the image content key and decrypt that encrypted image. That includes a physical attacker with debug or RAM access, or code later running on the device. This weakens image-encryption key confidentiality (and so the confidentiality of the encrypted image's plaintext). The device's long-term private decryption key is not exposed, and image authenticity is not affected. The fix wipes the context with bootutil_wipe_memory().
CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Productos afectados
mcu-tools · mcubootCVEs relacionadas — mcu-tools mcuboot
En el mismo producto, de las más peligrosas a las menos.
CVE-2026-16662LOWUninitialised bootloader stack disclosed into the measured-boot attestation record via a short EXPECTED_HASH TLV in MCUbootEPSS 0.2%CVE-2026-16664MEDIUMUnchecked serial-recovery image index causes out-of-bounds slot-table read in MCUboot Zephyr portEPSS 0.2%CVE-2026-127916LOWMCUboot image hash span is not bounded against the slot, allowing a read past the flash area during image validationEPSS 0.2%CVE-2026-127915LOWTLV iterator does not bound each entry against the declared TLV area in MCUboot bootutilEPSS 0.1%CVE-2024-32883HIGHMCUboot Injection attack of unprotected TLV valuesEPSS 0.1%CVE-2026-16671LOWOut-of-bounds stack write in MCUboot split-image validation with SHA-384/SHA-512 buildsEPSS 0.1%