CVE-2026-45812

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-07-24. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 5 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

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

Incorrect Calculation of Buffer Size vulnerability in Apache NimBLE when processing Legacy Advertising Report HCI event.

When a single HCI advertising report event bundles multiple reports, NimBLE miscalculated the offset to the next report. This can cause the host to read past the end of the buffer and deliver a GAP event with bogus data to the application.

Severity is low: NimBLE's own controller never batches multiple reports into one event, so this only matters when NimBLE's host is paired with a third-party controller that does.

This issue affects Apache NimBLE: through 1.9.0.

Users are recommended to upgrade to version 1.10.0, which fixes the issue.

CVSS v3
6.5
EG Score
6.5(high)
EG Risk
29(Track)
EG Risk 29/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
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

July 24, 2026

Last Modified

July 27, 2026

Advisory Details (2)

Auto-updated Jul 24, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit

commit 605c7585408b (apache/mynewt-nimble)

Fix landed in apache/mynewt-nimble commit 605c7585408b — awaiting tagged release

https://github.com/apache/mynewt-nimble/commit/605c7585408bc3674818eeb7b6f478a8aefe9746

Vendor Advisories for CVE-2026-45812(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 18× 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-07-27 15:01 UTCEG score recompute
  2. 2026-07-27 15:00 UTCGHSA enrichment
  3. 2026-07-27 14:13 UTCEPSS rescore
  4. 2026-07-27 01:26 UTCEG score recompute
  5. 2026-07-27 01:26 UTCGHSA enrichment
  6. 2026-07-26 14:54 UTCEPSS rescore
  7. 2026-07-26 14:54 UTCEPSS rescore
  8. 2026-07-26 03:03 UTCEG score recompute
  9. 2026-07-26 03:02 UTCGHSA enrichment
  10. 2026-07-25 14:18 UTCEPSS rescore
  11. 2026-07-24 18:33 UTCEG score recompute 6.50
  12. 2026-07-24 18:32 UTCGHSA enrichment
  13. 2026-07-24 18:31 UTCMITRE cvelistV5CVSS v3 → 6.5 · severity → MEDIUM
  14. 2026-07-24 16:11 UTCNVD update
  15. 2026-07-24 15:13 UTCMITRE cvelistV5
  16. 2026-07-24 14:12 UTCNVD update
  17. 2026-07-24 12:42 UTCEG score recompute
  18. 2026-07-24 12:41 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-45812?
CVE-2026-45812 is a medium vulnerability published on July 24, 2026. Incorrect Calculation of Buffer Size vulnerability in Apache NimBLE when processing Legacy Advertising Report HCI event. When a single HCI advertising report event bundles multiple reports, NimBLE miscalculated the offset to the next report. This can cause the host to read past the end of the…
When was CVE-2026-45812 disclosed?
CVE-2026-45812 was first published in the National Vulnerability Database on July 24, 2026, with the most recent update on July 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45812 actively exploited?
CVE-2026-45812 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 80.2% of all scored CVEs.
What is the CVSS score of CVE-2026-45812?
CVE-2026-45812 has a CVSS v3.1 base score of 6.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-45812?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45812, 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-45812

Explore →

Is Your Infrastructure Affected by CVE-2026-45812?

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