Due to a mistake in libcurl's WebSocket code, a malicious server can send a particularly crafted packet which makes libcurl get trapped in an endless busy-loop.
There is no other way for the application to escape or exit this loop other than killing the thread/process.
This might be used to DoS libcurl-using application.
{
"sources": [
{
"published": "2025-06-07T08:15:20.687Z",
"database_specific": {
"status": "Analyzed"
},
"imported": "2026-05-02T08:39:49.407Z",
"html_url": "https://nvd.nist.gov/vuln/detail/CVE-2025-5399",
"url": "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2025-5399",
"id": "CVE-2025-5399",
"modified": "2025-07-30T19:41:33.457Z"
},
{
"published": "2025-06-07T09:30:18Z",
"imported": "2026-05-02T08:42:42.714Z",
"html_url": "https://github.com/advisories/GHSA-8h93-38hx-vv92",
"url": "https://api.github.com/advisories/GHSA-8h93-38hx-vv92",
"id": "GHSA-8h93-38hx-vv92",
"modified": "2025-07-30T21:32:41Z"
},
{
"html_url": "https://euvd.enisa.europa.eu/vulnerability/EUVD-2025-17371",
"imported": "2026-05-02T08:42:17.767Z",
"published": "2025-06-07T07:49:09Z",
"id": "EUVD-2025-17371",
"modified": "2025-06-09T13:20:29Z",
"url": "https://euvdservices.enisa.europa.eu/api/enisaid?id=EUVD-2025-17371"
}
],
"license": "CC-BY-4.0"
}