CVE-2019-9512: golang.org/x/net/http vulnerable to ping floods
Summary
CVE-2019-9512: Reset flood in net/http and golang.org/x/net/http. Affects stdlib across 2 version ranges.
< 1.11.13
>= 1.12.0-0, < 1.12.8
Fixed in 1.11.13 or 1.12.8, depending on the release line you run. How to fix ↓
Also tracked for
- golang.org/x/net · Go
- golang.org/x/net · Go
- nodejs · Alpine:v3.10
- nodejs · Alpine:v3.10
The same CVE-2019-9512 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The golang.org/x/net/http package is a part of the Go ecosystem and provides functionality for HTTP communication. It is commonly used for building web servers and clients in Go applications. This package includes support for HTTP/2, which is a protocol for efficient communication between clients and servers. However, certain versions of the golang.org/x/net/http package are vulnerable to ping floods, which can lead to a denial of service (DoS) attack. An attacker can send continuous pings to an HTTP/2 peer, causing the peer to build an internal queue of responses. This can consume excessive CPU and memory resources, potentially impacting the availability and performance of the affected application.
Vulnerability Detail
The vulnerability arises from the inefficient queuing of responses to continuous pings in the HTTP/2 implementation of the golang.org/x/net/http package. When an attacker sends a large number of pings to an HTTP/2 peer, the peer's internal queue of responses grows, consuming significant CPU and memory resources. This can result in a DoS condition where the affected application becomes unresponsive or experiences degraded performance. The severity of this vulnerability is rated as HIGH with a CVSS score of 7.5.
How To Fix
Latest published version: go1.25.5 as of 22 Oct 2026
go get stdlib@vgo1.25.5Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
< 1.11.131.11.13go get stdlib@v1.11.13 -
>= 1.12.0-0, < 1.12.81.12.8go get stdlib@v1.12.8
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
There is no specific workaround mentioned for this vulnerability. However, as a general best practice, it is recommended to implement rate limiting or request throttling mechanisms in the application to mitigate the impact of DoS attacks.
Conclusion
The golang.org/x/net/http package is vulnerable to ping floods, which can lead to a denial of service (DoS) attack. It is recommended to update the package to version 0.0.0-20190813141303-74dc4d7220e7 or a later version to mitigate the risk. Implementing rate limiting or request throttling mechanisms in the application can also help mitigate the impact of DoS attacks. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for stdlib →
FAQ
The golang.org/x/net/http package is a part of the Go ecosystem and provides functionality for HTTP communication. It is commonly used for building web servers and clients in Go applications.
HTTP/2 is a protocol for efficient communication between clients and servers. It introduces features like multiplexing, server push, and header compression to improve performance over HTTP/1.1.
A ping flood is a type of DoS attack where an attacker sends a large number of ping requests to a target, overwhelming its resources and causing it to become unresponsive or slow.
An attacker can exploit this vulnerability by sending continuous pings to an HTTP/2 peer using the golang.org/x/net/http package. This causes the peer to build an internal queue of responses, consuming excessive CPU and memory resources.
The impact of this vulnerability can be a denial of service (DoS) condition where the affected application becomes unresponsive or experiences degraded performance due to the consumption of excessive CPU and memory resources.
References
Related vulnerabilities
Recent vulnerabilities recorded for stdlib.
