CVE-2026-5589

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 88% 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: cisa-adp, epss
6.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.3Exploit: NoneExposed: 0

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

An integer underflow in bt_mesh_sol_recv() in the Bluetooth Mesh solicitation handling (subsys/bluetooth/mesh/solicitation.c) leads to an out-of-bounds write. When CONFIG_BT_MESH_OD_PRIV_PROXY_SRV is enabled, the function parses solicitation PDUs from raw BLE advertising payloads. The AD parsing loop reads an attacker-controlled length byte (reported_len) and computes reported_len - 3 without checking that reported_len >= 3. When reported_len is less than 3, the subtraction is performed in signed int arithmetic and yields a negative value that bypasses the length guard and is then implicitly converted to a very large size_t when passed to net_buf_simple_pull_mem(). In builds without assertions, this wraps the buffer length and advances the data pointer far out of bounds, so subsequent reads dereference invalid memory. A nearby BLE device can trigger this with a non-connectable advertisement carrying a UUID16 AD structure and a crafted length byte, with no pairing or prior association required, potentially leading to denial of service or arbitrary code execution.

CVSS v3
6.3
EG Score
6.3(medium)
EPSS
12.3%
KEV
Not listed

Published

June 4, 2026

Last Modified

July 8, 2026

Advisory Details (1)

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

Out-of-bounds write caused by an integer underflow in the Bluetooth Mesh subsystem. · Advisory · zephyrproject-rtos/zephyr · GitHub

https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-4pm9-4v7f-x6gr

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 63× 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-15 16:57 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-15 02:00 UTCEPSS rescore
  4. 2026-07-14 03:21 UTCEG score recompute
  5. 2026-07-13 22:31 UTCEPSS rescore
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-13 06:13 UTCEPSS rescore
  8. 2026-07-12 05:46 UTCEPSS rescore
  9. 2026-07-11 11:45 UTCEG score recompute
  10. 2026-07-11 08:27 UTCEPSS rescore
  11. 2026-07-11 08:27 UTCEPSS rescore
  12. 2026-07-09 19:10 UTCEPSS rescore
  13. 2026-07-09 19:10 UTCEPSS rescore
  14. 2026-07-08 15:16 UTCEPSS rescore
  15. 2026-07-08 15:16 UTCEPSS rescore
  16. 2026-07-08 09:32 UTCEG score recompute
  17. 2026-07-07 13:46 UTCEPSS rescore
  18. 2026-07-07 13:46 UTCEPSS rescore
  19. 2026-07-06 16:27 UTCEPSS rescore
  20. 2026-07-06 16:27 UTCEPSS rescore
  21. 2026-07-06 02:23 UTCEPSS rescore
  22. 2026-07-06 02:23 UTCEPSS rescore
  23. 2026-07-06 02:18 UTCEG score recompute
  24. 2026-07-05 02:31 UTCEPSS rescore
  25. 2026-07-05 02:30 UTCEPSS rescore
Show 60 more
  1. 2026-07-04 06:31 UTCEPSS rescore
  2. 2026-07-04 06:31 UTCEPSS rescore
  3. 2026-07-03 00:21 UTCEG score recompute
  4. 2026-07-01 23:13 UTCEG score recompute
  5. 2026-07-01 15:07 UTCEPSS rescore
  6. 2026-06-30 23:22 UTCEPSS rescore
  7. 2026-06-30 20:56 UTCEG score recompute
  8. 2026-06-29 19:24 UTCEG score recompute
  9. 2026-06-29 14:06 UTCEPSS rescore
  10. 2026-06-28 17:17 UTCEG score recompute
  11. 2026-06-28 14:07 UTCEPSS rescore
  12. 2026-06-28 04:56 UTCEPSS rescore
  13. 2026-06-27 16:10 UTCEG score recompute
  14. 2026-06-27 03:08 UTCEPSS rescore
  15. 2026-06-26 14:55 UTCEG score recompute
  16. 2026-06-25 13:49 UTCEPSS rescore
  17. 2026-06-25 10:26 UTCEG score recompute
  18. 2026-06-24 14:05 UTCEPSS rescore
  19. 2026-06-24 08:59 UTCEG score recompute
  20. 2026-06-23 21:33 UTCEPSS rescore
  21. 2026-06-23 21:33 UTCEPSS rescore
  22. 2026-06-23 01:53 UTCEG score recompute
  23. 2026-06-22 14:25 UTCEPSS rescore
  24. 2026-06-22 14:25 UTCEPSS rescore
  25. 2026-06-21 14:56 UTCEPSS rescore
  26. 2026-06-21 14:56 UTCEPSS rescore
  27. 2026-06-21 01:59 UTCEPSS rescore
  28. 2026-06-21 01:59 UTCEPSS rescore
  29. 2026-06-19 19:46 UTCEG score recompute
  30. 2026-06-19 19:26 UTCEPSS rescore
  31. 2026-06-19 19:26 UTCEPSS rescore
  32. 2026-06-18 17:52 UTCEPSS rescore
  33. 2026-06-18 17:52 UTCEPSS rescore
  34. 2026-06-18 10:08 UTCEG score recompute
  35. 2026-06-17 17:53 UTCEPSS rescore
  36. 2026-06-17 09:02 UTCEG score recompute
  37. 2026-06-16 17:53 UTCEPSS rescore
  38. 2026-06-16 07:51 UTCEG score recompute
  39. 2026-06-15 17:49 UTCEPSS rescore
  40. 2026-06-15 17:49 UTCEPSS rescore
  41. 2026-06-15 06:43 UTCEG score recompute
  42. 2026-06-14 23:18 UTCEPSS rescore
  43. 2026-06-14 05:37 UTCEG score recompute
  44. 2026-06-13 23:00 UTCEPSS rescore
  45. 2026-06-13 04:29 UTCEG score recompute
  46. 2026-06-12 23:12 UTCEPSS rescore
  47. 2026-06-12 23:12 UTCEPSS rescore
  48. 2026-06-12 03:22 UTCEG score recompute
  49. 2026-06-11 14:00 UTCEPSS rescore
  50. 2026-06-11 02:15 UTCEG score recompute
  51. 2026-06-10 22:19 UTCEPSS rescore
  52. 2026-06-10 13:22 UTCEPSS rescore
  53. 2026-06-10 01:08 UTCEG score recompute
  54. 2026-06-09 00:02 UTCEG score recompute
  55. 2026-06-08 14:17 UTCEPSS rescore
  56. 2026-06-07 22:55 UTCEG score recompute 6.30
  57. 2026-06-07 15:25 UTCEPSS rescore
  58. 2026-06-06 13:47 UTCEPSS rescore
  59. 2026-06-05 22:47 UTCEPSS rescore
  60. 2026-06-04 20:10 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-5589?
CVE-2026-5589 is a medium vulnerability published on June 4, 2026. An integer underflow in btmeshsolrecv() in the Bluetooth Mesh solicitation handling (subsys/bluetooth/mesh/solicitation.c) leads to an out-of-bounds write. When CONFIGBTMESHODPRIVPROXYSRV is enabled, the function parses solicitation PDUs from raw BLE advertising payloads. The AD parsing loop reads…
When was CVE-2026-5589 disclosed?
CVE-2026-5589 was first published in the National Vulnerability Database on June 4, 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-5589 actively exploited?
CVE-2026-5589 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 12.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-5589?
CVE-2026-5589 has a CVSS v3.1 base score of 6.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-5589?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-5589, 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-5589

Explore →

Is Your Infrastructure Affected by CVE-2026-5589?

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