CVE-2026-10641

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% 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, secondary
Elevated
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: Elevated riskExposed: 0

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

Zephyr's Bluetooth Classic Hands-Free Profile (HFP) Hands-Free role parser (subsys/bluetooth/host/classic/hfp_hf.c) contains an out-of-bounds write. During Service Level Connection setup the HF sends AT+CIND=? and parses the AG's +CIND: response in cind_handle(), which assigns a per-entry counter index and calls cind_handle_values() for each list element. cind_handle_values() then wrote hf->ind_table[index] = i without verifying that index is within the 20-element int8_t ind_table[] array of struct bt_hfp_hf. Because the parser places no cap on the number of +CIND: list entries, a remote Attendant Gateway (a malicious, compromised, or spoofed peer the device connects to over Bluetooth) can send a response with more than 20 recognized indicator entries and drive index arbitrarily large, writing a small attacker-positioned value past the array into adjacent struct fields (feature masks, SDP/version state, the calls[] array, work/atomic bookkeeping) and potentially beyond the static connection pool slot. This yields memory corruption and at least denial of service of the Bluetooth host, triggered by a single malformed AT response with no user interaction. The sibling consumer ag_indicator_handle_values() already performed the equivalent bounds check; this commit adds the same index >= ARRAY_SIZE(hf->ind_table) guard to close the gap. Affects builds with CONFIG_BT_HFP_HF enabled; introduced with the original HFP HF CIND parser (~v1.7) and present through v4.4.0.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
48(Track)
EG Risk 48/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
Severity71% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

June 17, 2026

Last Modified

July 14, 2026

Advisory Details (2)

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

Out-of-bounds write in Bluetooth Classic HFP HF +CIND response parser during SLC setup · Advisory · zephyrproject-rtos/zephyr · GitHub

https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-wx5j-q6f2-59p3
github_commit

commit cf7693a8261a (zephyrproject-rtos/zephyr)

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

https://github.com/zephyrproject-rtos/zephyr/commit/cf7693a8261ae363c9cf46cfd51005486637173e

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 31× 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.

Showing the most recent 100 of 121 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-10641?
CVE-2026-10641 is a high vulnerability published on June 17, 2026. Zephyr's Bluetooth Classic Hands-Free Profile (HFP) Hands-Free role parser (subsys/bluetooth/host/classic/hfphf.c) contains an out-of-bounds write. During Service Level Connection setup the HF sends AT+CIND=? and parses the AG's +CIND: response in cindhandle(), which assigns a per-entry counter…
When was CVE-2026-10641 disclosed?
CVE-2026-10641 was first published in the National Vulnerability Database on June 17, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10641 actively exploited?
CVE-2026-10641 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 79.3% of all scored CVEs.
What is the CVSS score of CVE-2026-10641?
CVE-2026-10641 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-10641?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10641, 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-10641

Explore →

Is Your Infrastructure Affected by CVE-2026-10641?

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