Back

MEDIUM

predictable WebSocket mask

Published Sep 12, 2025

Description

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 products

Remediation

Red Hat statement

To exploit this issue, a curl application must be communicating through a defective proxy that confuses a WebSocket for HTTP traffic. Additionally, this flaw requires the traffic to be done using clear text HTTP / WebSocket (ws://) and not over TLS (wss://).

Red Hat mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Metrics

Weaknesses (1)

References (10)

Change history (0)

No recorded changes yet.

Sources
CVE.org / MITRE
Status PUBLISHED
Assigner curl
Published Sep 12, 2025
Updated Sep 15, 2026
Reserved Sep 9, 2025
CISA Vulnrichment
Updated Sep 12, 2025
NVD
Status Modified
Modified Sep 15, 2026
Red Hat
Severity Low
Public date Sep 12, 2025