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.
CVE-2026-11586
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.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- —
- EPSS
- 54.7%
- KEV
- Not listed
Published
July 3, 2026
Last Modified
July 7, 2026
Advisory Details (3)
Auto-updated Jul 6, 2026curl - WS Auto-PONG memory exhaustion - CVE-2026-11586
https://curl.se/docs/CVE-2026-11586.htmlVendor Advisories for CVE-2026-11586(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- GHSA-c68q-h477-5646GitHub Security AdvisoriesHigh
By default, curl automatically responds to WebSocket PING frames. Because curl lacks an upper...
- RHSA-2026:34975Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- RHSA-2026:29017Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
Patch Availability(3)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | libcurl4t64 (8.14.1-2ubuntu1.5) @ questing | 2026-07-16 | ubuntu |
| redhat | rust-main-1.96.1-1.hum1 | 2026-07-02 | redhat |
| redhat | curl-main-8.21.0-0.1.hum1 | 2026-06-24 | redhat |
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 11× in last 7d / 56× 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.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 00:36 UTCVendor advisory
- 2026-07-17 00:36 UTCGHSA enrichment
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-16 11:58 UTCVendor advisory
- 2026-07-16 11:58 UTCGHSA enrichment
- 2026-07-15 23:19 UTCVendor advisory
- 2026-07-15 23:19 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 10:41 UTCVendor advisory
- 2026-07-15 10:40 UTCGHSA enrichment
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 21:55 UTCVendor advisory
- 2026-07-14 21:55 UTCGHSA enrichment
- 2026-07-14 09:16 UTCVendor advisory
- 2026-07-14 09:16 UTCGHSA enrichment
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 20:37 UTCVendor advisory
- 2026-07-13 20:37 UTCGHSA enrichment
- 2026-07-13 07:58 UTCVendor advisory
Show 31 moreShow fewer
- 2026-07-13 07:58 UTCGHSA enrichment
- 2026-07-13 06:12 UTCEPSS rescore
- 2026-07-12 19:19 UTCVendor advisory
- 2026-07-12 19:19 UTCGHSA enrichment
- 2026-07-12 06:40 UTCVendor advisory
- 2026-07-12 06:40 UTCGHSA enrichment
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 18:01 UTCVendor advisory
- 2026-07-11 18:00 UTCGHSA enrichment
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 05:21 UTCVendor advisory
- 2026-07-11 05:21 UTCGHSA enrichment
- 2026-07-10 16:42 UTCVendor advisory
- 2026-07-10 16:42 UTCGHSA enrichment
- 2026-07-10 04:04 UTCVendor advisory
- 2026-07-10 04:04 UTCGHSA enrichment
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 15:24 UTCEG score recompute▲ 7.50
- 2026-07-09 15:24 UTCVendor advisory
- 2026-07-09 15:24 UTCGHSA enrichment
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 15:36 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
- 2026-07-06 11:57 UTCGHSA enrichment
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-03 08:29 UTCEG score recompute
- 2026-07-03 08:26 UTCNVD updatefirst tracked
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0414NVD 0.0EG 9.0EPSS 100%NONE
- CVE-2001-0550NVD 0.0EG 7.3EPSS 99%NONE
- CVE-2001-0731NVD 0.0EG 4.4EPSS 99%NONE
- CVE-2001-0554NVD 0.0EG 1.3EPSS 98%NONE
- CVE-2001-0010NVD 0.0EG 0.3EPSS 98%NONE
- CVE-2001-1174EG 0.0EPSS 90%NONE
- CVE-2001-1175EG 0.0NONE
- CVE-2001-0887EG 0.0NONE
- CVE-2001-0869EG 0.0NONE
- CVE-2001-0872EG 0.0NONE
Same CWE
10 shownCWE-770
- CVE-2018-20033EG 9.8CRITICAL
- CVE-2019-11479NVD 7.5EG 9.0EPSS 100%HIGH
- CVE-2019-11478NVD 5.3EG 9.0EPSS 100%MEDIUM
- CVE-2019-10088EG 8.8EPSS 91%HIGH
- CVE-2018-15462EG 8.6HIGH
- CVE-2018-15460EG 8.6HIGH
- CVE-2018-0137EG 8.6HIGH
- CVE-2008-5180NVD 5.3EG 7.9EPSS 99%MEDIUM
- CVE-2019-10094EG 7.8HIGH
- CVE-2018-16865EG 7.8HIGH
Frequently asked(5)
What is CVE-2026-11586?
When was CVE-2026-11586 disclosed?
Is CVE-2026-11586 actively exploited?
What is the CVSS score of CVE-2026-11586?
How do I remediate CVE-2026-11586?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-11586
Is Your Infrastructure Affected by CVE-2026-11586?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.