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 80% 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.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 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)
EPSS
20.2%
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 22× in last 7d / 94× 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-16 00:50 UTCEG score recompute
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 13:16 UTCEG score recompute
  4. 2026-07-15 02:00 UTCEPSS rescore
  5. 2026-07-15 01:34 UTCEG score recompute
  6. 2026-07-14 14:02 UTCEG score recompute
  7. 2026-07-14 02:30 UTCEG score recompute
  8. 2026-07-13 22:30 UTCEPSS rescore
  9. 2026-07-13 14:57 UTCEG score recompute
  10. 2026-07-13 06:12 UTCEPSS rescore
  11. 2026-07-13 03:25 UTCEG score recompute
  12. 2026-07-12 15:53 UTCEG score recompute
  13. 2026-07-12 05:46 UTCEPSS rescore
  14. 2026-07-12 04:19 UTCEG score recompute
  15. 2026-07-11 16:37 UTCEG score recompute
  16. 2026-07-11 08:27 UTCEPSS rescore
  17. 2026-07-11 05:05 UTCEG score recompute
  18. 2026-07-10 17:32 UTCEG score recompute
  19. 2026-07-10 05:59 UTCEG score recompute
  20. 2026-07-09 19:10 UTCEPSS rescore
  21. 2026-07-09 18:26 UTCEG score recompute
  22. 2026-07-09 06:48 UTCEG score recompute
  23. 2026-07-08 19:16 UTCEG score recompute
  24. 2026-07-08 15:15 UTCEPSS rescore
  25. 2026-07-08 15:15 UTCEPSS rescore
Show 69 more
  1. 2026-07-08 07:39 UTCEG score recompute
  2. 2026-07-07 20:08 UTCEG score recompute
  3. 2026-07-07 13:46 UTCEPSS rescore
  4. 2026-07-07 03:08 UTCEG score recompute
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 15:35 UTCEG score recompute
  7. 2026-07-06 03:37 UTCEG score recompute
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 15:55 UTCEG score recompute
  10. 2026-07-05 04:23 UTCEG score recompute
  11. 2026-07-05 02:30 UTCEPSS rescore
  12. 2026-07-05 02:30 UTCEPSS rescore
  13. 2026-07-04 16:18 UTCEG score recompute
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-04 04:45 UTCEG score recompute
  16. 2026-07-03 16:38 UTCEG score recompute
  17. 2026-07-03 05:06 UTCEG score recompute
  18. 2026-07-02 17:34 UTCEG score recompute
  19. 2026-07-02 06:00 UTCEG score recompute
  20. 2026-07-01 18:27 UTCEG score recompute
  21. 2026-07-01 15:06 UTCEPSS rescore
  22. 2026-07-01 15:06 UTCEPSS rescore
  23. 2026-07-01 06:54 UTCEG score recompute
  24. 2026-06-30 23:22 UTCEPSS rescore
  25. 2026-06-30 19:21 UTCEG score recompute
  26. 2026-06-30 07:49 UTCEG score recompute
  27. 2026-06-29 20:17 UTCEG score recompute
  28. 2026-06-29 14:06 UTCEPSS rescore
  29. 2026-06-29 08:45 UTCEG score recompute
  30. 2026-06-28 21:12 UTCEG score recompute
  31. 2026-06-28 14:07 UTCEPSS rescore
  32. 2026-06-28 09:40 UTCEG score recompute
  33. 2026-06-28 04:56 UTCEPSS rescore
  34. 2026-06-28 04:56 UTCEPSS rescore
  35. 2026-06-27 22:08 UTCEG score recompute
  36. 2026-06-27 10:36 UTCEG score recompute
  37. 2026-06-27 03:08 UTCEPSS rescore
  38. 2026-06-26 23:03 UTCEG score recompute
  39. 2026-06-26 11:31 UTCEG score recompute
  40. 2026-06-25 20:54 UTCEG score recompute
  41. 2026-06-25 13:49 UTCEPSS rescore
  42. 2026-06-25 09:21 UTCEG score recompute
  43. 2026-06-24 21:49 UTCEG score recompute
  44. 2026-06-24 14:05 UTCEPSS rescore
  45. 2026-06-24 10:17 UTCEG score recompute
  46. 2026-06-23 22:34 UTCEG score recompute
  47. 2026-06-23 21:32 UTCEPSS rescore
  48. 2026-06-23 11:01 UTCEG score recompute
  49. 2026-06-22 23:28 UTCEG score recompute
  50. 2026-06-22 14:25 UTCEPSS rescore
  51. 2026-06-22 14:25 UTCEPSS rescore
  52. 2026-06-22 11:55 UTCEG score recompute
  53. 2026-06-22 00:19 UTCEG score recompute
  54. 2026-06-21 14:56 UTCEPSS rescore
  55. 2026-06-21 14:56 UTCEPSS rescore
  56. 2026-06-21 12:44 UTCEG score recompute
  57. 2026-06-21 01:59 UTCEPSS rescore
  58. 2026-06-21 01:59 UTCEPSS rescore
  59. 2026-06-21 01:11 UTCEG score recompute
  60. 2026-06-20 13:39 UTCEG score recompute
  61. 2026-06-20 02:07 UTCEG score recompute
  62. 2026-06-19 19:25 UTCEPSS rescore
  63. 2026-06-19 14:17 UTCEG score recompute
  64. 2026-06-19 02:43 UTCEG score recompute
  65. 2026-06-18 17:52 UTCEPSS rescore
  66. 2026-06-18 15:10 UTCEG score recompute
  67. 2026-06-18 03:29 UTCEG score recompute
  68. 2026-06-17 15:57 UTCEG score recompute
  69. 2026-06-17 15:52 UTCNVD updatefirst tracked

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 20.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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.