CVE-2026-11586Published Jul 3, 2026 · Jul 3Updated Nov 3
WS Auto-PONG memory exhaustion
curl
High7.5Fix available
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| curl curl |
| No fix yet |
| curl curl |
| No fix yet |
| curl curl |
|
curl
| Product | Affected | Fixed in |
|---|---|---|
| curl curl |
| No fix yet |
| curl curl |
| No fix yet |
| curl curl |
|
8.17.08.16.0| No fix yet |
By default, curl automatically responds to WebSocket PING frames. Because curl lacks an upper bound on memory allocation for unacknowledged frames, a malicious server can exhaust all available memory by flooding curl with rapid, sequential PING messages.
From the CVE record · curl
curl automatically responds to WebSocket PING frames but does not limit memory allocated for unacknowledged frames. A malicious server can exhaust available memory by sending rapid, sequential PING frames to a connected curl client.
Engineers running curl with WebSocket connections should check whether their installations are affected; the affected versions are not specified.