VulnerabilityPublished 13 Nov 2026

CVE-2026-16662: mcu-tools mcuboot · Info-leak

Affects mcu-tools mcubootSource CVE Database V5

Compare

Not known to be exploited · CVSS 2.4 Low : upgrade to 2.5.0 when convenient.

Data as of 13 Nov 2026, 01:45 UTC

CVSS 3.1 base score

2.4Low

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (zephyr)	CVSS 3.1	2.4

Patch: Available – fixed in 2.5.0

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Physical
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade mcu-tools mcuboot to 2.5.0.

Affected software

Product	Affected	Fixed in
mcu-toolsmcuboot	Affected >=1.6.0 <2.5.0	Fixed in 2.5.0
GitHubmcuboot`pkg:github/mcuboot`Other threats	Affected >=1.6.0 <2.5.0	Fixed in 2.5.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to mcuboot version 2.5.0 or later, which rejects EXPECTED_HASH_TLV entries with incorrect lengths, eliminating the information leak. If upgrading is not immediately possible, ensure that primary-slot validation is enabled (the default in Zephyr) to prevent malformed images from reaching the vulnerable code path. No other mitigation is required as the vulnerability requires physical or flash-write access and does not impact integrity or availability.

Description

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.

Impact

An attacker with physical or flash-write access can cause up to 63 bytes of uninitialized bootloader stack memory to be included in the boot record measurement field sent to a remote attestation verifier. This information leak exposes internal bootloader state but does not affect the integrity or availability of the boot process or attestation. The vulnerability is low severity and considered a defense-in-depth disclosure.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Nov 2026, 00:52 UTC

Technical details

References

Community reviews

Related threats