CVE-2026-10651

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 93% 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, nvd
Trending — 3 sources updated this week
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

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

A malformed Bluetooth Classic SDP attribute can trigger a reachable assertion in Zephyr's SDP parser. In subsys/bluetooth/host/classic/sdp.c, bt_sdp_parse_attribute() accepts an input buffer once it contains the 1-byte attribute type and 2-byte attribute id, but then unconditionally pulls an additional byte for the value type without verifying that the byte is present. A truncated 3-byte attribute (for example 09 00 09) therefore reaches net_buf_simple_pull() with insufficient remaining length, triggering the __ASSERT_NO_MSG(buf->len >= len) check and a kernel panic in assert-enabled builds (denial of service). In builds where assertions are disabled, parsing may continue past the end of the available buffer, leading to an out-of-bounds read and undefined behavior.

CVSS v3
6.5
EG Score
6.5(medium)
EPSS
6.9%
KEV
Not listed

Published

June 22, 2026

Last Modified

July 6, 2026

Advisory Details (1)

Auto-updated Jun 23, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Bluetooth Classic SDP parser truncation bug in bt_sdp_parse_attribute() leads to reachable assertion and possible out-of-bounds read · Advisory · zephyrproject-rtos/zephyr · GitHub

https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-p93g-3r68-cj53

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 58× 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-12 05:46 UTCEPSS rescore
  2. 2026-07-11 20:20 UTCEG score recompute
  3. 2026-07-11 08:27 UTCEPSS rescore
  4. 2026-07-10 22:31 UTCEG score recompute
  5. 2026-07-10 00:40 UTCEG score recompute
  6. 2026-07-09 19:10 UTCEPSS rescore
  7. 2026-07-09 02:49 UTCEG score recompute
  8. 2026-07-08 15:15 UTCEPSS rescore
  9. 2026-07-08 15:15 UTCEPSS rescore
  10. 2026-07-08 05:00 UTCEG score recompute
  11. 2026-07-07 13:46 UTCEPSS rescore
  12. 2026-07-07 06:57 UTCEG score recompute▼ 0.60
  13. 2026-07-06 21:35 UTCNVD updateCVSS v3 → 6.5 · severity → MEDIUM
  14. 2026-07-06 18:45 UTCEG score recompute
  15. 2026-07-06 16:27 UTCEPSS rescore
  16. 2026-07-06 05:41 UTCEG score recompute
  17. 2026-07-06 02:23 UTCEPSS rescore
  18. 2026-07-05 17:29 UTCEG score recompute
  19. 2026-07-05 05:18 UTCEG score recompute
  20. 2026-07-05 02:30 UTCEPSS rescore
  21. 2026-07-05 02:30 UTCEPSS rescore
  22. 2026-07-04 16:51 UTCEG score recompute
  23. 2026-07-04 06:31 UTCEPSS rescore
  24. 2026-07-04 04:17 UTCEG score recompute
  25. 2026-07-03 16:06 UTCEG score recompute
Show 33 more
  1. 2026-07-03 03:55 UTCEG score recompute
  2. 2026-07-02 15:42 UTCEG score recompute
  3. 2026-07-02 03:31 UTCEG score recompute
  4. 2026-07-01 15:21 UTCEG score recompute
  5. 2026-07-01 15:06 UTCEPSS rescore
  6. 2026-07-01 15:06 UTCEPSS rescore
  7. 2026-07-01 03:11 UTCEG score recompute
  8. 2026-06-30 23:22 UTCEPSS rescore
  9. 2026-06-30 15:00 UTCEG score recompute
  10. 2026-06-30 02:50 UTCEG score recompute
  11. 2026-06-29 14:40 UTCEG score recompute
  12. 2026-06-29 14:06 UTCEPSS rescore
  13. 2026-06-29 02:30 UTCEG score recompute
  14. 2026-06-28 14:19 UTCEG score recompute
  15. 2026-06-28 14:07 UTCEPSS rescore
  16. 2026-06-28 04:56 UTCEPSS rescore
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-28 02:09 UTCEG score recompute
  19. 2026-06-27 13:58 UTCEG score recompute
  20. 2026-06-27 03:08 UTCEPSS rescore
  21. 2026-06-27 01:46 UTCEG score recompute
  22. 2026-06-26 13:35 UTCEG score recompute
  23. 2026-06-26 01:26 UTCEG score recompute
  24. 2026-06-25 13:49 UTCEPSS rescore
  25. 2026-06-25 13:16 UTCEG score recompute
  26. 2026-06-25 01:05 UTCEG score recompute
  27. 2026-06-24 14:05 UTCEPSS rescore
  28. 2026-06-24 12:55 UTCEG score recompute
  29. 2026-06-24 00:44 UTCEG score recompute
  30. 2026-06-23 21:32 UTCEPSS rescore
  31. 2026-06-23 12:33 UTCEG score recompute
  32. 2026-06-23 00:22 UTCEG score recompute
  33. 2026-06-23 00:20 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-10651?
CVE-2026-10651 is a medium vulnerability published on June 22, 2026. A malformed Bluetooth Classic SDP attribute can trigger a reachable assertion in Zephyr's SDP parser. In subsys/bluetooth/host/classic/sdp.c, btsdpparseattribute() accepts an input buffer once it contains the 1-byte attribute type and 2-byte attribute id, but then unconditionally pulls an…
When was CVE-2026-10651 disclosed?
CVE-2026-10651 was first published in the National Vulnerability Database on June 22, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10651 actively exploited?
CVE-2026-10651 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-10651?
CVE-2026-10651 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-10651?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10651, 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-10651

Explore →

Is Your Infrastructure Affected by CVE-2026-10651?

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

Start Free Scan →Browse All CVEs