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.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Alpine Linux | — | Upgrade curl | Jul 6, 2026 | Jul 3, 2026 |
| Amazon_linux_2023 | — | Upgrade libcurl-minimal-debuginfoUpgrade curlUpgrade curl-debugsourceUpgrade libcurl-minimalUpgrade curl-minimal-debuginfoUpgrade libcurl-debuginfoUpgrade libcurlUpgrade libcurl-develUpgrade curl-minimalUpgrade curl-debuginfo | Sep 30, 2026 | Jul 3, 2026 |
| Redhat_linux | — | No solution exists | Jul 17, 2026 | Jul 3, 2026 |
| Ubuntu | — | Upgrade libcurl4-openssl-devUpgrade curlUpgrade libcurl3t64-gnutlsUpgrade libcurl4t64Upgrade libcurl4-gnutls-dev | Jul 12, 2026 | Jul 9, 2026 |
| Vmware Photon_os | — | Use 'tdnf update' to upgrade all packages to the latest version. | Aug 13, 2026 | Jul 3, 2026 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub