CVE-2025-10148: predictable WebSocket mask

Published Sep 10, 2025
·
Updated

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.

Affected Software

8 affected componentsFixes available
curl curl
haxx curl>=8.11.0<8.16.0
Microsoft azl3 cmake 3.30.3-10
Microsoft cbl2 curl 8.8.0-6
Microsoft azl3 curl 8.11.1-4
Microsoft azl3 cmake 3.30.3-9
Microsoft azl3 curl 8.11.1-3
Microsoft cbl2 curl 8.8.0-7

Event History

Sep 11, 2025
CVE Published
via Microsoft·08:01 AM
Data Sourced
via Microsoft·08:01 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:01 AM
Affected Software
Updated
via Microsoft·08:01 AM
Affected Software
Updated
via Microsoft·08:01 AM
DescriptionSeverity
Sep 12, 2025
CVE Published
via MITRE·05:10 AM
Data Sourced
via MITRE·05:10 AM
DescriptionWeakness
Data Sourced
via NVD·06:15 AM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-10148?

CVE-2025-10148 is considered to be of medium severity due to the potential for traffic manipulation by a malicious server.

2

How do I fix CVE-2025-10148?

To fix CVE-2025-10148, update to the latest version of curl that has addressed the websocket mask pattern issue.

3

What is the impact of CVE-2025-10148?

The impact of CVE-2025-10148 is that it allows a malicious server to induce traffic, potentially leading to data exposure.

4

Which versions of curl are affected by CVE-2025-10148?

CVE-2025-10148 affects all versions of curl that utilize the websocket code with the flawed mask pattern.

5

Is there a workaround for CVE-2025-10148?

Currently, there are no official workarounds for CVE-2025-10148 other than upgrading to a patched version of curl.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203