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.
References
| Link | Resource |
|---|---|
| https://curl.se/docs/CVE-2025-5399.html | Vendor Advisory |
| https://curl.se/docs/CVE-2025-5399.json | Vendor Advisory |
| https://hackerone.com/reports/3168039 | Exploit Issue Tracking Third Party Advisory |
| http://www.openwall.com/lists/oss-security/2025/06/04/2 | Mailing List Third Party Advisory |
Configurations
History
No history.
Information
Published : 2025-06-07 08:15
Updated : 2025-07-30 19:41
NVD link : CVE-2025-5399
Mitre link : CVE-2025-5399
CVE.ORG link : CVE-2025-5399
JSON object : View
Products Affected
haxx
- curl
CWE
CWE-835
Loop with Unreachable Exit Condition ('Infinite Loop')
