# CVE-2026-11809: UpdateHub probe: uninitialized-heap out-of-bounds read of network-supplied metadata

> A malicious UpdateHub server can trigger an out-of-bounds read in the Zephyr RTOS OTA client, causing a device crash and denial of service.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-6r86-hvv2-h6g4

## What is CVE-2026-11809?

CVE-2026-11809 is a low-severity memory corruption vulnerability in zephyrproject zephyr, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The UpdateHub OTA client in subsys/mgmt/updatehub/updatehub.c contains an out-of-bounds / uninitialized-memory read in z_impl_updatehub_probe(). The probe response from the UpdateHub server is copied into a heap buffer (metadata) that is correctly NUL-terminated, but a second buffer (metadata_copy) is allocated with k_malloc (unzeroed) and filled with memcpy(metadata_copy, metadata, strlen(metadata)), which omits the terminating NUL. Everything after the copied content remains uninitialized heap.

When the first json_obj_parse() over the array descriptor fails, the code falls back to json_obj_parse(metadata_copy, strlen(metadata_copy), ...). The strlen() call scans past the copied bytes through uninitialized heap and, if no zero byte is found before the end of the allocation, reads beyond the buffer; the resulting over-long length is then parsed as JSON. The probe payload is fully controlled by the (malicious, compromised, or — without the optional CONFIG_UPDATEHUB_DTLS — on-path) UpdateHub server, which can craft a large payload that fails the first parse to drive this path.

The consequence is a read of uninitialized heap, with a worst case of an out-of-bounds read past the metadata_copy allocation that can fault and crash the update thread/device, producing a network-triggerable denial of service. The over-read data is consumed only internally to evaluate the update and is not returned to the attacker, so there is no direct information disclosure and no out-of-bounds write.

The fix zeroes metadata_copy with memset before the copy, guaranteeing NUL termination and bounding strlen() within the allocation.

Weakness: CWE-908 (Use of Uninitialized Resource), CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2026-11809 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-11809 is a low-severity memory corruption vulnerability in zephyrproject zephyr, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-11809 in the wild and no public exploit code.

Affected product: zephyrproject zephyr. 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-11809/ (Markdown: https://insights.sbomify.com/CVE-2026-11809/index.md)
```

## Sources

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

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