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_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.

Score
CVSS 3.1 2.4 Low
Status
Awaiting Analysis - vulnerabilities@zephyrproject.org
Published
2026-11-13
Last modified
2026-11-17
Weaknesses
CWE-457

Affected products

References


Your early warning system for new security vulnerabilities


Open BETA

Every day brings a flood of new vulnerabilities, roughly 100 CVEs daily. Which one will really affect you?

Attacks on known but unpatched vulnerabilities (Common Vulnerabilities and Exposures, or CVEs for short) are among the most common entry points for hackers. Companies must continuously check for such vulnerabilities. Does this affect our products? Which versions are affected? How critical is it?

As the window between publication and exploitation by attackers keeps shrinking, companies are under more pressure than ever to find a high-quality solution for managing these risks as quickly as possible. However, IT teams are heavily time-constrained, making manual tracking of all relevant CVEs nearly impossible.

100+ new CVEs per day

Most CVEs are irrelevant to your infrastructure

Time-to-exploit < 5 days

Attackers are exploiting vulnerabilities faster than ever before

Manual research is time-consuming

Vendor websites, RSS feeds, and blogs need to be searched daily

Vulnerability scanners are lagging behind

Plugin development isn't progressing fast enough to identify risks in a timely manner

CVE Alarm provides you with immediate notifications of relevant security vulnerabilities

CVE Alarm continuously monitors all newly published CVEs and automatically compares them with the products you use. You will only be notified if a relevant vulnerability affects your systems and meets your defined criteria.

Real-time notification

Direct email notification without delay

Product-based filters

Only CVEs that actually affect your infrastructure

Custom criteria

Filter by CVSS-Score, exposure, products, and vendors

Team-oriented & multi-tenant capable

Assign products or alerts to specific teams or customers

More time to act

Administrators can review and install updates faster

Time savings

No more manually reviewing the flood of new CVE information

Three steps for better patch planning

With CVE Alarm you will easily receive relevant security alerts for your infrastructure.

Subscribe To
Products

Select the IT products you use. From Apache to VMware – all critical assets are monitored.

Define
Criteria

Set product-specific filters based on criticality (CVSS ≥ 7.0 (high)). You will only receive relevant alerts.

Get
Notified

Receive an immediate notification as soon as a matching CVE appears. Recipients can be defined individually for each product.

Be faster
than the attackers

With CVE information, you have more time for patch planning and can close security gaps before they are exploited.

Designed for the target group companies and service providers

Whether a global Security Operations Center or a small IT team, CVE Alarm supports CVE monitoring for organizations of all sizes.

Companies with their own IT infrastructure

Medium-sized to large companies that need to proactively monitor their vulnerabilities

Administrators

IT professionals responsible for infrastructure security and maintenance

Security teams and cybersecurity experts

Security Operations Centers (SOCs) and Computer Emergency Response Teams (CERTs) that require CVE information for proactive security measures

Chief Information Security Officers (CISOs) & IT managers

Decision-makers who need an overview of critical vulnerabilities

Security service providers

Managed service providers (MSPs) and security consultancies that manage multiple clients and need to monitor CVEs

From experience to innovation. About us and CVE Alarm.

CVE Alarm is a product of AVABIS GmbH and was developed in collaboration with IT security experts.

AVABIS GmbH – Who are we?
We, AVABIS GmbH, are an experienced partner for IT quality assurance. Our focus is on software testing and software development. Our clients, corporations from various industries, have trusted us for more than ten years.

CVE Alarm – How did the idea come about?
In our daily project work, we repeatedly witnessed the significant uncertainty surrounding new security alerts. We saw how much time teams have to invest to determine whether a published vulnerability even affects their own system landscape. Based on these experiences, we know how time-consuming it is to gather, evaluate, and prioritize information from diverse sources under time pressure.

This made us realize that the real problem is not a lack of information, but rather an overabundance of it.

This led to the idea of ​​developing a product that enables companies to manage this information overload and maintain control over their IT security.

Developed and operated in Germany
Our systems run on German IT infrastructure, and we adhere to high security and data protection standards. This ensures data sovereignty, clear responsibilities, and reliability, especially for organizations with their own security teams or CERT structures.

Get in contact with our team

Do you have questions about CVE Alarm or would you like a personal consultation?
We're happy to help.

Please use our contact form.