# CVE-2026-127915: TLV iterator does not bound each entry against the declared TLV area in MCUboot bootutil


- **Severity:** Low 2.0 (`CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-4fp3-3qw2-25jv

## What is CVE-2026-127915?

CVE-2026-127915 is a low-severity vulnerability in mcu-tools mcuboot, published on 13 Nov 2026. 

### Official description

The MCUboot TLV iterator bootutil_tlv_iter_next() in boot/bootutil/src/tlv.c walks image trailer TLVs with a single loop guard (it->tlv_off < it->tlv_end) and advances by sizeof(struct image_tlv) + tlv.it_len using the attacker-controlled it_len field, without validating that the entry's header or payload stays within it->tlv_end. As a result the 4-byte header read can extend up to 3 bytes past the declared TLV area, and the returned (off, len) can describe a payload that runs past it.

The path is pre-authentication: TLVs are parsed during bootutil_img_validate() before the signature is verified, and a crafted image can be presented through DFU / serial-recovery / OTA. However the impact is contained by surrounding guards: bootutil_img_validate() first rejects a TLV area larger than bootutil_max_image_size(), the default LOAD_IMAGE_DATA sink is flash_area_read() which bounds-checks against the flash partition and fails an out-of-partition read, and every payload consumer (EXPECTED_HASH_TLV, EXPECTED_KEY_TLV, EXPECTED_SIG_TLV, IMAGE_TLV_SEC_CNT) clamps len against a fixed buffer before copying.

The residual effect in a default flash build is therefore an out-of-region read confined to the attacker's own slot partition whose result is never observable, yielding at worst a clean validation failure rather than memory corruption or information disclosure. A genuine (though still bounded) out-of-bounds read remains under the non-default MCUBOOT_RAM_LOAD configuration, where LOAD_IMAGE_DATA is an unchecked memcpy. The fix is to validate each entry's header and payload against it->tlv_end inside the iterator.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-127915?


## How do I fix CVE-2026-127915?

No fix has been published for CVE-2026-127915 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-127915 being exploited?

There is no known exploitation of CVE-2026-127915 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-127915 and fix it if it is affected.

What it is: CVE-2026-127915 is a low-severity vulnerability in mcu-tools mcuboot, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-127915 in the wild and no public exploit code.

Affected product: mcu-tools mcuboot. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-127915/ (Markdown: https://insights.sbomify.com/CVE-2026-127915/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-127915
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-127915
- OSV: https://osv.dev/vulnerability/CVE-2026-127915

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-127915/
Summaries are generated and may contain mistakes; the official description above is the record.
