CVE-2026-11586

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM 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(medium)
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
40%
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
ubuntulibcurl4-openssl-dev (7.35.0-1ubuntu2.20+esm21) @ trusty2026-08-21ubuntu
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.

Affected Packages

(2 across 2 ecosystems)
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
curl8.21.0-r0
Debian:14(1)
PackageVulnerable rangeFixed inDependents
curl8.14.1-2 ... 8.21.0~rc2-1+exp1 (61 versions)8.21.0~rc3-1

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 39× in last 7d / 154× 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 209 total refreshes for this CVE.

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

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 59.7% 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

See which npm, PyPI, Go, and Maven packages are affected by 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.