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 75% 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
Trending — 3 sources updated this weekElevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: Elevated riskExposed: 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)
EG Risk
56(Track)
EG Risk 56/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
Severity88% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

June 4, 2026

Last Modified

July 22, 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 7× in last 7d / 30× 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 144 total refreshes for this CVE.

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

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 22, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 75.1% of all scored CVEs.
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