PULSE
FEED
ransomqilin reclama a A.I.M Cash & Carry · IE · Retail & E-Commerceransomsilentransomgroup reclama a Q...ransomcurious worm reclama a interdent.com · DE · Healthcareransomrhysida reclama a Waterman Group · GB · Professional Servicesransomransomhouse reclama a Indiabulls Housing Finance · IN · Financial Servicesransomqilin reclama a Power Equipment · AU · Manufacturingransomqilin reclama a Arrigoni SpA · IT · Manufacturingransomplay reclama a Acudor · US · Manufacturingransompanzer reclama a Bjbsayariahransomdaixin reclama a Trustbridge & EmpathHealth · US · Healthcareransomrhysida reclama a Steffen family retail group · Retail & E-Commerceransomincransom reclama a BHIC Bofors Asia · MY · Government & Defenseransomakira reclama a The Mandrel Group · Otherransomn0n reclama a Verastem Oncology (Verastem, Inc.) · US · Healthcareransomqilin reclama a A.I.M Cash & Carry · IE · Retail & E-Commerceransomsilentransomgroup reclama a Q...ransomcurious worm reclama a interdent.com · DE · Healthcareransomrhysida reclama a Waterman Group · GB · Professional Servicesransomransomhouse reclama a Indiabulls Housing Finance · IN · Financial Servicesransomqilin reclama a Power Equipment · AU · Manufacturingransomqilin reclama a Arrigoni SpA · IT · Manufacturingransomplay reclama a Acudor · US · Manufacturingransompanzer reclama a Bjbsayariahransomdaixin reclama a Trustbridge & EmpathHealth · US · Healthcareransomrhysida reclama a Steffen family retail group · Retail & E-Commerceransomincransom reclama a BHIC Bofors Asia · MY · Government & Defenseransomakira reclama a The Mandrel Group · Otherransomn0n reclama a Verastem Oncology (Verastem, Inc.) · US · Healthcare
← Todos los CVEs
CVE Watch13 nov 2026

CVE-2026-16662

boot_save_boot_status() in boot/bootutil/src/boot_record.c reads the image's EXPECTED_HASH_TLV into a stack buffer image_hash[IMAGE_HASH_SIZ

CVSS

2.4

Bajo

EPSS

0.1%

p3

KEV

—

Exploit Today

1

0-100

Publicado: 13 nov 2026 · Última mod.: 13 nov 2026 · CWE-457

EPSS · 30d
0.1%EPSS · 30 días0.1%
2026-11-132026-11-15
Descripción técnica

boot_save_boot_status() in boot/bootutil/src/boot_record.c reads the image's EXPECTED_HASH_TLV into a stack buffer image_hash[IMAGE_HASH_SIZE] that is never zero-initialised. The TLV handler validates only the upper bound (len > sizeof(image_hash)) and then reads exactly len bytes, so a TLV shorter than IMAGE_HASH_SIZE leaves the tail of image_hash holding stale stack content. The subsequent copy into the boot record, memcpy(buf + offset, image_hash, sizeof(image_hash)), uses the fixed buffer size rather than len, so up to IMAGE_HASH_SIZE - 1 bytes of uninitialised bootloader stack are written into the measured-boot record. The defect is reachable only under MCUBOOT_MEASURED_BOOT, and only when nothing has checked the length of the hash TLV before boot_save_boot_status() reads it. bootutil_img_validate() rejects a hash TLV whose length is not exactly sizeof(hash) (boot/bootutil/src/image_validate.c:345), and primary-slot validation is on by default (Zephyr's CONFIG_BOOT_VALIDATE_SLOT0 defaults to y), so in a default build the malformed image never reaches this code. Two kinds of build let a short TLV through: Builds that use pure signatures (MCUBOOT_SIGN_PURE, Zephyr CONFIG_BOOT_SIGNATURE_TYPE_PURE). The signature covers the image itself, so the hash-TLV check in bootutil_img_validate() is compiled out, and a pure-signed image normally carries no hash TLV. A hash TLV is still allowed in the unprotected TLV area, which the signature does not cover, so a short one can be added to a correctly signed image without invalidating it. This applies with every upgrade strategy, including direct-XIP and RAM-load, and the modified image can be delivered through any path that accepts a signed image. Builds with primary-slot validation turned off: the swap and overwrite loader built without MCUBOOT_VALIDATE_PRIMARY_SLOT, which checks only the image magic before calling boot_add_shared_data(), and the Zephyr single-slot loader (boot/zephyr/single_loader.c) built without it, including the MCUBOOT_VALIDATE_PRIMARY_SLOT_ONCE variant, which skips validation once the trailer records an earlier successful one. Placing the crafted image requires physical or flash-write access to the device; in a single-slot build with serial recovery enabled, the serial-recovery upload writes the primary slot directly and can place it as well. Outside pure-signature builds, the direct-XIP and RAM-load strategies in boot/bootutil/src/loader.c validate the selected slot unconditionally and are not affected. It is also reachable through a time-of-check/time-of-use change to tamperable external flash between validation and the boot-record read. In these configurations the boot record's measurement is already not trustworthy: the hash copied into the record is the image's own EXPECTED_HASH_TLV, which nothing has verified and which the attacker chooses. The defect therefore does not weaken attestation integrity any further. What it adds is a path for bootloader memory to leave the device: up to 63 bytes (IMAGE_HASH_SIZE - 1) of uninitialised bootloader stack are embedded in the measurement field that a downstream attestation service sends to a remote verifier. In the configurations analysed the residue is bootloader internal state (TLV offsets and lengths, flash addresses, loop state), not key material, but what occupies that stack region depends on configuration and on which code ran before boot_save_boot_status(). It is reported as a low-severity, defense-in-depth disclosure with no integrity or availability impact. This is distinct from the already-fixed record_len integer underflow in the same routine (GHSA-8hrv-4cp5-4rg3). The fix rejects any EXPECTED_HASH_TLV whose length is not exactly IMAGE_HASH_SIZE.

Referencias oficiales
CVEs relacionados
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2026-287316.5 MED
—
———A memory corruption vulnerability exists in VideoLAN VLC 3.0.23. A specially crafted Interplay MVE file can trigger a condition that allows access to a variable that is not explicitly initialized, which under certain conditions can lead to code execution in the context of the current process.7h
CVE-2026-466765.3 MED
19.8%
——6BACnet Stack is a BACnet open source protocol stack C library for embedded systems. From versions 1.4.0 to before 1.4.4, and 1.5.0 to before 1.5.1, an uninitialized value use vulnerability in bacnet-stack's AtomicReadFile record-access ACK encoder allows unauthenticated remote attackers to corrupt the encoded OCTET STRING length and payload boundary in network responses by sending a crafted AtomicReadFile request that reaches a successful record-access path. This issue has been patched in versions 1.4.4 and 1.5.1.4d
CVE-2026-1269157.5 ALT
23.2%
——7Use of uninitialized variable in Skia in Google Chrome on on Android prior to 157.0.8103.78 allowed a remote attacker who had compromised the renderer process to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)3d
CVE-2026-588102.3 BAJ
0.1%
——0In multiple functions of simd_ctx.c, there is a possible way to disclose secure vector predicate and fault registers to non-secure callers due to uninitialized data. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for exploitation.3d
CVE-2026-88822—
8.7%
——3Issue summary: QUIC, when performing automated peer detection, may allow uninitialized stack data to leak into the received address which is then used as the destination for outgoing packets. Impact summary: Applications using QUIC's automated peer detection mechanism may receive an invalid address, leading to connection loss and disclosure of uninitialized stack data to an attacker observing the outgoing network traffic. CWE: CWE-457 (Use of Uninitialized Variable) Description: The OpenSSL QUIC stack contains a feature in which, when using an already connected socket, it will auto-detect the peer address during the SSL handshake. This feature uses the getpeername() function, passing a buffer of sufficient length to hold any supported address family, but passes a buffer length that is only sized such that larger addresses, such as IPv6, cannot be retrieved. The getpeername() function however, still returns the full address length, which is accepted as the valid input buffer length, leading to the address buffer containing uninitialized stack data instead of the actual peer address. The invalid peer address is then used as destination for the outgoing packets which leads to a connectivity breakage and a leakage of the uninitialized stack data to passive network observers. FIPS impact: no The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as the affected protocol is not implemented in the FIPS module.6d
CVE-2026-1216116.5 MED
47.4%
——14A flaw was found in GStreamer's gst-plugins-bad package. A use of uninitialized memory vulnerability exists in the H.265 (HEVC) bitstream parser when processing Video Parameter Sets that declare more than one HRD (Hypothetical Reference Decoder) parameter set. A remote attacker could exploit this by providing a crafted H.265 media file or stream that, when processed by an application using GStreamer, causes unpredictable parser behavior and may crash the application. This can lead to a denial of service for any application using GStreamer to play back H.265 content.6d