CVE-2025-10148
MEDIUMDescription
curl's websocket code did not update the 32 bit mask pattern for each new outgoing frame as the specification says. Instead it used a fixed mask that persisted and was used throughout the entire connection. A predictable mask pattern allows for a malicious server to induce traffic between the two communicating parties that could be interpreted by an involved proxy (configured or transparent) as genuine, real, HTTP traffic with content and thereby poison its cache. That cached poisoned content could then be served to all users of that proxy.
Is your site exposed to CVE-2025-10148?
Run a free security scan — no signup, results in seconds.
CVSS v3.1 Score
Affected Products
| Vendor | Product |
|---|---|
| haxx | curl |
References
Advisories & Patches
Frequently Asked Questions
What is CVE-2025-10148? +
How severe is CVE-2025-10148? +
What products are affected by CVE-2025-10148? +
How do I check if I'm vulnerable to CVE-2025-10148? +
Related Vulnerabilities
The curl logic that works with SASL authentication could end up cleaning up the GSASL context *twice* without clearing the …
libcurl had a flaw that when instructed to clear proxy authentication credentials which made it not do so, leaving the …
A use-after-free vulnerability exists in libcurl when an application configures an HTTP/2 stream-dependency tree via `CURLOPT_STREAM_DEPENDS` or `CURLOPT_STREAM_DEPENDS_E`, subsequently invokes …
Successfully using libcurl to do a transfer to a specific HTTP origin (`hostA`) with **Digest** authentication and then changing the …
libcurl keeps previously used connections in a connection pool for subsequent transfers to reuse if one of them matches the …
A flaw in curl’s cookie parsing logic allows a malicious HTTP server to set 'super cookies' that bypass the Public …