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.
{
"license": "CC-BY-4.0",
"sources": [
{
"database_specific": {
"status": "Analyzed"
},
"html_url": "https://nvd.nist.gov/vuln/detail/CVE-2026-11586",
"id": "CVE-2026-11586",
"imported": "2026-08-07T19:54:38.779Z",
"modified": "2026-07-07T17:59:46.920Z",
"published": "2026-07-03T07:16:23.883Z",
"url": "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-11586"
},
{
"html_url": "https://github.com/advisories/GHSA-c68q-h477-5646",
"id": "GHSA-c68q-h477-5646",
"imported": "2026-08-07T19:55:59.532Z",
"modified": "2026-07-07T18:31:40Z",
"published": "2026-07-03T09:31:25Z",
"url": "https://api.github.com/advisories/GHSA-c68q-h477-5646"
},
{
"html_url": "https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-41500",
"id": "EUVD-2026-41500",
"imported": "2026-08-07T19:55:07.145Z",
"modified": "2026-07-06T15:16:27Z",
"published": "2026-07-03T06:13:04Z",
"url": "https://euvdservices.enisa.europa.eu/api/enisaid?id=EUVD-2026-41500"
}
]
}