CVE-2026-127916 is a vulnerability in mcuboot's bootutil_img_hash() function where image size fields are summed and used to read flash memory without proper bounds checking. This can cause out-of-bounds reads up to 64 KB past the image slot or more on certain code paths, potentially causing read faults during image validation. The flaw exists because the image is hashed before signature verification, allowing an attacker who can place an image in a slot to trigger the issue. The vulnerability is fixed in mcuboot version 2.5.0 by adding safe addition and bounds checks before hashing.
CVE-2026-127915 is a low-severity vulnerability in the MCUboot bootloader's TLV iterator function bootutil_tlv_iter_next(). It improperly validates bounds when parsing image trailer TLVs, allowing a crafted image to cause a bounded out-of-region read during pre-authentication. The impact is limited by multiple runtime checks and memory bounds enforcement in typical configurations, resulting in a validation failure rather than memory corruption or data disclosure. The vulnerability is fixed in MCUboot version 2.5.0.
CVE-2026-16664 is a vulnerability in MCUboot's Zephyr serial-recovery upload handler that allows an out-of-bounds read on a static array due to lack of range checking on a host-supplied image index. This can cause a denial of service via a bus/hard fault or potentially allow unauthorized erase/write operations on non-image partitions. The flaw affects the default non-direct upload path on the Zephyr port with array-backed slot layout and impacts versions from 2.0.0 onward. The vulnerability is exploitable by anyone with access to the unauthenticated serial/SMP recovery console. A fix involves rejecting out-of-range image indices before slot lookup and adding bounds checks in the slot indexing function.
CVE-2026-16659 is a memory-safety vulnerability in MCUboot's serial-recovery image-upload handler affecting certain encrypted image builds on Zephyr and Mynewt ports. The flaw occurs when early validation failures cause a NULL pointer dereference in the bootloader's recovery code, leading to a transient denial of service. This issue does not allow memory corruption or information disclosure and only affects non-default builds with encrypted images and serial recovery enabled. The vulnerability is fixed in MCUboot version 2.5.0.
CVE-2026-16671 is a memory safety vulnerability in the mcuboot bootloader component of mcu-tools. It involves a fixed-size buffer overflow in the split_image_check() function when configured with certain non-default cryptographic digest algorithms larger than 32 bytes. This overflow can corrupt the bootloader's stack, potentially causing instability or boot failure. The vulnerability does not allow attacker-controlled code execution due to the fixed and non-attacker-controlled overflow content. A fix is available in mcuboot version 2.5.0.
CVE-2026-16662 is an information leak vulnerability in mcuboot's boot_save_boot_status() function when MCUBOOT_MEASURED_BOOT is enabled and primary-slot validation is disabled. It causes uninitialized stack memory to be copied into the boot record's measurement field, potentially exposing internal bootloader state. The flaw requires physical or flash-write access to place a crafted image. The vulnerability is low severity with no impact on integrity or availability and is fixed in mcuboot version 2.5.0.
CVE-2026-128091 is an information leak vulnerability in MCUboot when built with the TinyCrypt crypto backend. The vulnerability arises because the AES-128 key schedule used for image encryption is not cleared from memory after boot, leaving sensitive key material accessible in RAM. This allows an attacker with physical or code-level access to recover the image content encryption key and decrypt the encrypted image. The device's long-term private keys and image authenticity are not impacted. A fix is available in MCUboot version 2.5.0 that wipes the key context from memory.
CVE-2026-127928 is an information leak vulnerability in MCUboot's encrypted image support combined with serial recovery. The vulnerability arises because the plaintext AES image key remains in stack memory after certain functions return, due to missing zeroization of sensitive data structures. An attacker with the ability to read device RAM, for example via a debug port, could recover the AES key and decrypt the protected firmware image. The device's long-term private decryption key is not exposed. Exploitation requires local memory-read access; no remote or protocol-based memory disclosure is known. The issue affects MCUboot versions from 1.9.0 up to but not including 2.5.0 and is fixed in version 2.5.0.