CVE-2026-11810

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 75% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The UpdateHub firmware-update agent's probe handler (z_impl_updatehub_probe() in subsys/mgmt/updatehub/updatehub.c) parses the JSON metadata returned by the update server into a fixed two-level nested-array struct. After parsing it validates only the outer array length (objects_len != 2) and then dereferences objects[1].objects[0].objects.sha256sum via strlen() without checking that the inner object array of element [1] is non-empty.

The metadata is attacker-influenceable network input: the agent fetches it over CoAP from the configured UpdateHub server during its routine OTA probe. A malicious or compromised update server (or, when DTLS is disabled, a network man-in-the-middle) can return a response whose second outer object array is empty. Because the parse target is zero-initialised, the corresponding objects[1].objects[0].objects.sha256sum pointer is NULL, and the subsequent strlen() dereferences address zero. The same defect exists in both the 'any boards' and 'some boards' metadata layouts.

The resulting CPU fault is fatal under Zephyr's default error handling, halting or resetting the device, so the flaw is a remotely triggerable denial of service. Impact is limited to availability; it is a read from NULL with no out-of-bounds write, memory corruption, or information disclosure. The fix rejects metadata whose inner object array is empty before any dereference, on both layouts.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 26, 2026

Advisory Details (2)

Auto-updated Aug 10, 2026
Patch available. Sources: github_commit, github.
github Patch Available

NULL-pointer dereference in UpdateHub OTA agent on empty inner metadata array (remote DoS) · Advisory · zephyrproject-rtos/zephyr · GitHub

https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-jfpc-324j-84ww
github_commit

commit 3424082022cb (zephyrproject-rtos/zephyr)

Fix landed in zephyrproject-rtos/zephyr commit 3424082022cb — awaiting tagged release

https://github.com/zephyrproject-rtos/zephyr/commit/3424082022cb39d568434021b1d6f68b6a7fb3bf

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 37× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:21 UTCEPSS rescore
  2. 2026-08-29 09:54 UTCEG score recompute
  3. 2026-08-28 21:40 UTCEPSS rescore
  4. 2026-08-27 16:40 UTCEG score recompute
  5. 2026-08-27 14:24 UTCEPSS rescore
  6. 2026-08-26 17:27 UTCEG score recompute
  7. 2026-08-25 20:59 UTCEG score recompute
  8. 2026-08-25 13:48 UTCEPSS rescore
  9. 2026-08-24 22:58 UTCEG score recompute
  10. 2026-08-24 11:58 UTCEG score recompute
  11. 2026-08-23 02:48 UTCEG score recompute
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-22 04:48 UTCEG score recompute
  14. 2026-08-21 23:48 UTCEPSS rescore
  15. 2026-08-21 06:47 UTCEG score recompute
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-19 21:47 UTCEG score recompute
  18. 2026-08-19 17:03 UTCEPSS rescore
  19. 2026-08-18 23:46 UTCEG score recompute
  20. 2026-08-18 13:48 UTCEPSS rescore
  21. 2026-08-17 14:39 UTCEG score recompute
  22. 2026-08-16 16:40 UTCEG score recompute
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 05:38 UTCEG score recompute
  25. 2026-08-16 02:14 UTCEPSS rescore
Show 12 more
  1. 2026-08-15 07:39 UTCEG score recompute
  2. 2026-08-15 01:30 UTCEPSS rescore
  3. 2026-08-13 22:38 UTCEG score recompute
  4. 2026-08-13 22:00 UTCEPSS rescore
  5. 2026-08-13 00:38 UTCEG score recompute
  6. 2026-08-12 13:50 UTCEPSS rescore
  7. 2026-08-11 15:37 UTCEG score recompute
  8. 2026-08-11 14:57 UTCEG score recompute
  9. 2026-08-11 13:42 UTCEPSS rescore
  10. 2026-08-10 21:32 UTCEG score recompute
  11. 2026-08-10 20:35 UTCEG score recompute
  12. 2026-08-10 20:34 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-11810?
CVE-2026-11810 is a high vulnerability published on August 10, 2026. The UpdateHub firmware-update agent's probe handler (zimplupdatehubprobe() in subsys/mgmt/updatehub/updatehub.c) parses the JSON metadata returned by the update server into a fixed two-level nested-array struct. After parsing it validates only the outer array length (objectslen != 2) and then…
When was CVE-2026-11810 disclosed?
CVE-2026-11810 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-11810 actively exploited?
CVE-2026-11810 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 74.6% of all scored CVEs.
What is the CVSS score of CVE-2026-11810?
CVE-2026-11810 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-11810?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-11810, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-11810

Explore →

Is Your Infrastructure Affected by CVE-2026-11810?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.