CVE-2026-45813

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 5 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

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

Out-of-bounds Write, Integer Underflow (Wrap or Wraparound) vulnerability in Apache NimBLE BASS service. Improper validation when parsing BASS service  "Add Source" and "Modify Source" operation PDU could results in stack buffer overflow or arbitrary out-of-bound read.

This can be triggered by nearby devices over Bluetooth connection, however pairing is required prior to accessing BASS service, which depending on device configuration may or may not require user action.

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
8.8
EG Score
8.8(high)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 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_pr.
github_pr

BASS operation parsing cleanups

Fix merged in apache/mynewt-nimble PR #2232 on 2026-05-15 — awaiting tagged release

https://github.com/apache/mynewt-nimble/pull/2232

Vendor Advisories for CVE-2026-45813(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-45813?
CVE-2026-45813 is a high vulnerability published on July 24, 2026. Out-of-bounds Write, Integer Underflow (Wrap or Wraparound) vulnerability in Apache NimBLE BASS service. Improper validation when parsing BASS service "Add Source" and "Modify Source" operation PDU could results in stack buffer overflow or arbitrary out-of-bound read. This can be triggered by…
When was CVE-2026-45813 disclosed?
CVE-2026-45813 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-45813 actively exploited?
CVE-2026-45813 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.5% of all scored CVEs.
What is the CVSS score of CVE-2026-45813?
CVE-2026-45813 has a CVSS v3.1 base score of 8.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-45813?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45813, 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-45813

Explore →

Is Your Infrastructure Affected by CVE-2026-45813?

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