CVE-2026-11586

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-03. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

By default, curl automatically responds to WebSocket PING frames. Because curl lacks an upper bound on memory allocation for unacknowledged frames, a malicious server can exhaust all available memory by flooding curl with rapid, sequential PING messages.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
39%
KEV
Not listed

Published

July 3, 2026

Last Modified

July 7, 2026

Advisory Details (3)

Auto-updated Jul 6, 2026
No patch confirmed yet.
generic

curl - WS Auto-PONG memory exhaustion - CVE-2026-11586

https://curl.se/docs/CVE-2026-11586.html

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibcurl4t64 (8.14.1-2ubuntu1.5) @ questing2026-07-26ubuntu
redhatrust-main-1.96.1-1.hum12026-07-02redhat
redhatcurl-main-8.21.0-0.1.hum12026-06-24redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 18× in last 7d / 72× 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-27 15:51 UTCEG score recompute
  2. 2026-07-27 15:51 UTCVendor advisory
  3. 2026-07-27 15:51 UTCGHSA enrichment
  4. 2026-07-27 14:13 UTCEPSS rescore
  5. 2026-07-27 01:37 UTCEG score recompute
  6. 2026-07-27 01:37 UTCVendor advisory
  7. 2026-07-27 01:37 UTCGHSA enrichment
  8. 2026-07-26 14:54 UTCEPSS rescore
  9. 2026-07-26 14:54 UTCEPSS rescore
  10. 2026-07-26 12:58 UTCEG score recompute
  11. 2026-07-26 12:58 UTCVendor advisory
  12. 2026-07-26 12:58 UTCGHSA enrichment
  13. 2026-07-25 14:17 UTCEPSS rescore
  14. 2026-07-24 14:17 UTCEPSS rescore
  15. 2026-07-23 14:18 UTCEPSS rescore
  16. 2026-07-23 03:04 UTCEG score recompute
  17. 2026-07-22 14:08 UTCEPSS rescore
  18. 2026-07-21 15:24 UTCEPSS rescore
  19. 2026-07-20 17:08 UTCEPSS rescore
  20. 2026-07-19 14:30 UTCEPSS rescore
  21. 2026-07-19 02:28 UTCEPSS rescore
  22. 2026-07-18 10:04 UTCEPSS rescore
  23. 2026-07-17 00:36 UTCVendor advisory
  24. 2026-07-17 00:36 UTCGHSA enrichment
  25. 2026-07-16 17:02 UTCEPSS rescore
Show 47 more
  1. 2026-07-16 11:58 UTCVendor advisory
  2. 2026-07-16 11:58 UTCGHSA enrichment
  3. 2026-07-15 23:19 UTCVendor advisory
  4. 2026-07-15 23:19 UTCGHSA enrichment
  5. 2026-07-15 16:57 UTCEPSS rescore
  6. 2026-07-15 10:41 UTCVendor advisory
  7. 2026-07-15 10:40 UTCGHSA enrichment
  8. 2026-07-15 02:00 UTCEPSS rescore
  9. 2026-07-14 21:55 UTCVendor advisory
  10. 2026-07-14 21:55 UTCGHSA enrichment
  11. 2026-07-14 09:16 UTCVendor advisory
  12. 2026-07-14 09:16 UTCGHSA enrichment
  13. 2026-07-13 22:30 UTCEPSS rescore
  14. 2026-07-13 20:37 UTCVendor advisory
  15. 2026-07-13 20:37 UTCGHSA enrichment
  16. 2026-07-13 07:58 UTCVendor advisory
  17. 2026-07-13 07:58 UTCGHSA enrichment
  18. 2026-07-13 06:12 UTCEPSS rescore
  19. 2026-07-12 19:19 UTCVendor advisory
  20. 2026-07-12 19:19 UTCGHSA enrichment
  21. 2026-07-12 06:40 UTCVendor advisory
  22. 2026-07-12 06:40 UTCGHSA enrichment
  23. 2026-07-12 05:46 UTCEPSS rescore
  24. 2026-07-11 18:01 UTCVendor advisory
  25. 2026-07-11 18:00 UTCGHSA enrichment
  26. 2026-07-11 08:27 UTCEPSS rescore
  27. 2026-07-11 05:21 UTCVendor advisory
  28. 2026-07-11 05:21 UTCGHSA enrichment
  29. 2026-07-10 16:42 UTCVendor advisory
  30. 2026-07-10 16:42 UTCGHSA enrichment
  31. 2026-07-10 04:04 UTCVendor advisory
  32. 2026-07-10 04:04 UTCGHSA enrichment
  33. 2026-07-09 19:10 UTCEPSS rescore
  34. 2026-07-09 15:24 UTCEG score recompute 7.50
  35. 2026-07-09 15:24 UTCVendor advisory
  36. 2026-07-09 15:24 UTCGHSA enrichment
  37. 2026-07-08 15:15 UTCEPSS rescore
  38. 2026-07-08 15:15 UTCEPSS rescore
  39. 2026-07-07 13:46 UTCEPSS rescore
  40. 2026-07-06 16:27 UTCEPSS rescore
  41. 2026-07-06 15:36 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  42. 2026-07-06 11:57 UTCGHSA enrichment
  43. 2026-07-06 02:23 UTCEPSS rescore
  44. 2026-07-05 02:30 UTCEPSS rescore
  45. 2026-07-05 02:30 UTCEPSS rescore
  46. 2026-07-03 08:29 UTCEG score recompute
  47. 2026-07-03 08:26 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-11586?
CVE-2026-11586 is a high vulnerability published on July 3, 2026. By default, curl automatically responds to WebSocket PING frames. Because curl lacks an upper bound on memory allocation for unacknowledged frames, a malicious server can exhaust all available memory by flooding curl with rapid, sequential PING messages.
When was CVE-2026-11586 disclosed?
CVE-2026-11586 was first published in the National Vulnerability Database on July 3, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-11586 actively exploited?
CVE-2026-11586 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 60.6% of all scored CVEs.
What is the CVSS score of CVE-2026-11586?
CVE-2026-11586 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-11586?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-11586, 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-11586

Explore →

Is Your Infrastructure Affected by CVE-2026-11586?

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