CVE-2026-10680

HIGHPre-NVD 7.67.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (4th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
7.6EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.6Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

The Classic (BR/EDR) L2CAP signaling handlers l2cap_br_conf_req() and l2cap_br_conf_rsp() in subsys/bluetooth/host/classic/l2cap_br.c validated the minimum command size against buf->len (the bytes remaining in the whole received PDU) instead of len (the per-command data length from the L2CAP signaling header). Because multiple signaling commands can be packed into one PDU, buf->len may exceed a command's len. An attacker can send a CONF_REQ command with a header length smaller than the configuration-request structure (e.g. 0), followed by another command so that buf->len still satisfies the check. The check then passes incorrectly and opt_len = len - sizeof(*req) underflows the uint16_t to a near-0xFFFF value. The configuration-option loop, which lacks an opt_len-versus-buf->len guard, then walks far past the end of the pooled ACL receive buffer using net_buf pull primitives that perform no runtime bounds check, producing an out-of-bounds read of host memory and, when the out-of-bounds option bytes encode an MTU or flush-timeout option, an out-of-bounds write. The BR/EDR signaling channel is processed before pairing/encryption and an L2CAP channel to an L0 service such as SDP can be opened without pairing, so an unauthenticated peer within radio range that can establish an ACL connection can trigger the flaw, leading to memory corruption and denial of service (host/device crash). The defect is present in released versions including v4.4.0. The fix validates against len instead of buf->len in both handlers.

CVSS v3
7.6
EG Score
7.6HIGHmedium confidence
EG Risk
34
EG Risk 34/100

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 (value × EchelonGraph’s weight)
Severity76% × 45%
The EG Score, 7.6 of 10.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 21, 2026

Last Modified

July 30, 2026

Advisory Details (2)

Auto-updated Jul 22, 2026
Fix referenced — no release confirmed yet. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Out-of-bounds access in Zephyr BR/EDR L2CAP configuration request handling via `uint16_t` length underflow · Advisory · zephyrproject-rtos/zephyr · GitHub

https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-vrwx-p97q-8854
GitHub commit

commit 1d451683377f (zephyrproject-rtos/zephyr)

Fix landed in zephyrproject-rtos/zephyr commit 1d451683377f — awaiting tagged release

https://github.com/zephyrproject-rtos/zephyr/commit/1d451683377f4c8e56d7718565bea7b5c1155159

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 34× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 123 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 23 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  2. 2026-10-12 16:39 UTCEG score recompute
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  4. 2026-10-11 20:14 UTCEG score recompute
  5. 2026-10-11 18:26 UTCEG score recompute
  6. 2026-10-11 15:00 UTCEG score recompute
  7. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  8. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  9. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  10. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  11. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  12. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  13. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  14. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  15. 2026-10-04 14:46 UTCEG score recompute
  16. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  17. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  18. 2026-10-01 07:25 UTCEG score recompute
  19. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  20. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  21. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  22. 2026-09-28 06:03 UTCEG score recompute
  23. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  24. 2026-09-24 03:19 UTCEG score recompute
  25. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
Show 75 more
  1. 2026-09-23 01:21 UTCEG score recompute
  2. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-09-20 05:54 UTCEG score recompute
  4. 2026-09-19 00:19 UTCEG score recompute
  5. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-09-18 03:46 UTCEG score recompute
  7. 2026-09-17 05:04 UTCEG score recompute
  8. 2026-09-16 12:33 UTCEG score recompute
  9. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  10. 2026-09-14 04:04 UTCEG score recompute
  11. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  12. 2026-09-13 02:48 UTCEG score recompute
  13. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  14. 2026-09-11 21:00 UTCEG score recompute
  15. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  16. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  17. 2026-09-11 08:52 UTCEG score recompute
  18. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  19. 2026-09-09 11:10 UTCEG score recompute
  20. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  21. 2026-09-07 22:27 UTCEG score recompute
  22. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  23. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  24. 2026-09-05 20:32 UTCEG score recompute
  25. 2026-09-05 08:25 UTCEG score recompute
  26. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  27. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  28. 2026-09-02 00:55 UTCEG score recompute
  29. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  30. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  31. 2026-08-31 03:25 UTCEG score recompute
  32. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  33. 2026-08-30 02:09 UTCEG score recompute
  34. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  35. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  36. 2026-08-28 02:26 UTCEG score recompute
  37. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  38. 2026-08-27 01:50 UTCEG score recompute
  39. 2026-08-26 01:04 UTCEG score recompute
  40. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  41. 2026-08-25 00:45 UTCEG score recompute
  42. 2026-08-24 12:36 UTCEG score recompute
  43. 2026-08-23 12:20 UTCEG score recompute
  44. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  45. 2026-08-21 23:50 UTCEG score recompute
  46. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  47. 2026-08-20 23:30 UTCEG score recompute
  48. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  49. 2026-08-19 23:15 UTCEG score recompute
  50. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  51. 2026-08-18 22:53 UTCEG score recompute
  52. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  53. 2026-08-17 22:38 UTCEG score recompute
  54. 2026-08-16 22:20 UTCEG score recompute
  55. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  56. 2026-08-16 10:11 UTCEG score recompute
  57. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  58. 2026-08-15 09:56 UTCEG score recompute
  59. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  60. 2026-08-14 09:39 UTCEG score recompute
  61. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  62. 2026-08-12 21:16 UTCEG score recompute
  63. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  64. 2026-08-11 21:00 UTCEG score recompute
  65. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  66. 2026-08-11 08:53 UTCEG score recompute
  67. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  68. 2026-08-09 20:29 UTCEG score recompute
  69. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  70. 2026-08-08 20:14 UTCEG score recompute
  71. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  72. 2026-08-07 19:58 UTCEG score recompute
  73. 2026-08-06 19:42 UTCEG score recompute
  74. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  75. 2026-08-05 19:26 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-10680?
CVE-2026-10680 is a high-severity vulnerability; its CVE record was published on July 21, 2026. The Classic (BR/EDR) L2CAP signaling handlers l2capbrconfreq() and l2capbrconfrsp() in subsys/bluetooth/host/classic/l2capbr.c validated the minimum command size against buf->len (the bytes remaining in the whole received PDU) instead of len (the per-command data length from the L2CAP signaling…
When was the CVE record for CVE-2026-10680 published?
The CVE record for CVE-2026-10680 was published on July 21, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 30, 2026; the record at its source may have been updated since.
Is CVE-2026-10680 actively exploited?
CVE-2026-10680 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-10680?
CVE-2026-10680 has a CVSS base score of 7.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-10680?
A fix for CVE-2026-10680 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-10680?

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

Book a Demo →Browse All CVEs