CVE-2026-10658

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (20th 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

Also known asEUVD-2026-38410 (ENISA EUVD)Source: ENISA EUVD

7.1EG
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.3%CVSS: 7.1Exploit: 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).

bt_iso_recv() in subsys/bluetooth/host/iso.c pulled the ISO SDU header (4 bytes) or, when the timestamp flag is set, the timestamped SDU header (8 bytes) from the inbound HCI ISO Data buffer via net_buf_pull_mem() without first checking buf->len. The upstream hci_iso() handler enforces buf->len == the controller-declared ISO Data_Load length, so a malicious or buggy controller / adjacent BLE peer on an established CIS/BIS can present a first-fragment (BT_ISO_START) or single (BT_ISO_SINGLE) PDU shorter than the SDU header. Because net_buf_simple_pull_mem only guards length with __ASSERT_NO_MSG (compiled out when CONFIG_ASSERT is disabled, the production default), the pull underflows buf->len (uint16_t, e.g. 0 - 8 = 0xFFF8) and advances buf->data past valid data: the subsequent reads of hdr->slen and hdr->sn are out-of-bounds reads of adjacent pool memory. For the multi-fragment (START) case the corrupted buffer is retained as iso->rx, and a following CONT/END fragment's net_buf_tailroom() guard underflows to a near-SIZE_MAX value, defeating the bounds check and causing net_buf_add_mem() to memcpy attacker-supplied fragment data far past the RX pool buffer (out-of-bounds write). The flaw affects ISO receive builds (CONFIG_BT_ISO_RX, selected by the default-off LE Audio options BT_ISO_PERIPHERAL/BT_ISO_CENTRAL/BT_ISO_SYNC_RECEIVER) and has existed since the ISO subsystem was introduced (v2.6.0) through v4.4.0. The fix adds explicit buf->len < sizeof(ts_hdr) and buf->len < sizeof(hdr) checks that drop the buffer before pulling.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.3%
EPSS %ILE
20th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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 partial (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)60 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 partial (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

June 22, 2026

Last Modified

October 25, 2026

Advisory Details (1)

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

Bluetooth Host ISO RX Missing SDU Header Length Validation in bt_iso_recv() Leads to DoS · Advisory · zephyrproject-rtos/zephyr · GitHub

https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-26g8-rmpf-j6cw

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 40× 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 160 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 60 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-10658?
CVE-2026-10658 is a high-severity vulnerability; its CVE record was published on June 22, 2026. btisorecv() in subsys/bluetooth/host/iso.c pulled the ISO SDU header (4 bytes) or, when the timestamp flag is set, the timestamped SDU header (8 bytes) from the inbound HCI ISO Data buffer via netbufpullmem() without first checking buf->len. The upstream hciiso() handler enforces buf->len == the…
When was the CVE record for CVE-2026-10658 published?
The CVE record for CVE-2026-10658 was published on June 22, 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 October 25, 2026; the record at its source may have been updated since.
Is CVE-2026-10658 actively exploited?
CVE-2026-10658 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-10658?
CVE-2026-10658 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-10658?
A fix for CVE-2026-10658 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-10658

Explore →

Is Your Infrastructure Affected by CVE-2026-10658?

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

Book a Demo →Browse All CVEs