CVE-2026-5068

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 64% 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
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

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

A remote, unauthenticated BLE peer can trigger a 2-byte out-of-bounds write in the Bluetooth host during L2CAP LE CoC SDU reassembly. When the application enables segmentation (via chan_ops.alloc_buf) and the chosen RX pool has a user_data_size smaller than 2 bytes, the segmentation counter stored in the net_buf user_data area is written out of bounds in l2cap_chan_le_recv_seg (subsys/bluetooth/host/l2cap.c). The observed effects are an AddressSanitizer abort and, without ASan, heap corruption / fatal error.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
36.4%
KEV
Not listed

Published

June 9, 2026

Last Modified

July 8, 2026

Advisory Details (1)

Auto-updated Jun 9, 2026
Patch available. Sources: github.
github Patch Available

bt: l2cap le coc: remote oob write via seg counter stored in net_buf user_data · Advisory · zephyrproject-rtos/zephyr · GitHub

https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-qrcq-hxwj-mqxm

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 95× 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 120 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-5068?
CVE-2026-5068 is a high vulnerability published on June 9, 2026. A remote, unauthenticated BLE peer can trigger a 2-byte out-of-bounds write in the Bluetooth host during L2CAP LE CoC SDU reassembly. When the application enables segmentation (via chanops.allocbuf) and the chosen RX pool has a userdatasize smaller than 2 bytes, the segmentation counter stored in…
When was CVE-2026-5068 disclosed?
CVE-2026-5068 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-5068 actively exploited?
CVE-2026-5068 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 36.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-5068?
CVE-2026-5068 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-5068?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-5068, 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-5068

Explore →

Is Your Infrastructure Affected by CVE-2026-5068?

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

Start Free Scan →Browse All CVEs