CVE-2026-5066

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 76% 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
Elevated
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 potential out-of-bounds write/read exists in the TLS socket connect path of the network sockets subsystem (subsys/net/lib/sockets/sockets_tls.c). When the TLS session cache is enabled, tls_session_store() and tls_session_restore() memcpy the caller-supplied address into a fixed-size buffer using the caller-controlled addrlen value without validating it against the destination size. struct net_sockaddr is an opaque type, so an application can pass an addrlen larger than sizeof(struct net_sockaddr) (for example 128 bytes into a 24-byte stack buffer), causing the memcpy to read and write past the end of the address memory used by the TLS session cache. This out-of-bounds write can lead to a crash and denial of service, and potentially to arbitrary code execution.

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

Published

June 4, 2026

Last Modified

July 8, 2026

Advisory Details (1)

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

net: sockets: tls: Potential out-of-bounds write/read in socket_op_vtable::connect function · Advisory · zephyrproject-rtos/zephyr · GitHub

https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-wgrc-jrf6-24f3

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-5066?
CVE-2026-5066 is a high vulnerability published on June 4, 2026. A potential out-of-bounds write/read exists in the TLS socket connect path of the network sockets subsystem (subsys/net/lib/sockets/socketstls.c). When the TLS session cache is enabled, tlssessionstore() and tlssessionrestore() memcpy the caller-supplied address into a fixed-size buffer using the…
When was CVE-2026-5066 disclosed?
CVE-2026-5066 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-5066 actively exploited?
CVE-2026-5066 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 24.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-5066?
CVE-2026-5066 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-5066?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-5066, 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-5066

Explore →

Is Your Infrastructure Affected by CVE-2026-5066?

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

Start Free Scan →Browse All CVEs