Update module golang.org/x/net to v0.55.0 [SECURITY] - #50
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
Contributor
Author
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
Bot
force-pushed
the
renovate/go-golang.org-x-net-vulnerability
branch
from
December 19, 2024 00:05
004e187 to
3aa9d0a
Compare
renovate
Bot
force-pushed
the
renovate/go-golang.org-x-net-vulnerability
branch
from
March 13, 2025 02:14
3aa9d0a to
301a8e0
Compare
renovate
Bot
force-pushed
the
renovate/go-golang.org-x-net-vulnerability
branch
from
April 8, 2025 13:27
301a8e0 to
776d841
Compare
renovate
Bot
force-pushed
the
renovate/go-golang.org-x-net-vulnerability
branch
from
April 16, 2025 21:47
776d841 to
a87289e
Compare
renovate
Bot
force-pushed
the
renovate/go-golang.org-x-net-vulnerability
branch
from
May 7, 2025 11:13
a87289e to
145110d
Compare
renovate
Bot
force-pushed
the
renovate/go-golang.org-x-net-vulnerability
branch
from
August 10, 2025 12:52
145110d to
66a6edd
Compare
renovate
Bot
force-pushed
the
renovate/go-golang.org-x-net-vulnerability
branch
from
October 9, 2025 15:29
66a6edd to
853bc63
Compare
renovate
Bot
force-pushed
the
renovate/go-golang.org-x-net-vulnerability
branch
2 times, most recently
from
November 17, 2025 02:35
853bc63 to
da5d85e
Compare
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
Bot
force-pushed
the
renovate/go-golang.org-x-net-vulnerability
branch
2 times, most recently
from
January 23, 2026 04:33
da5d85e to
c114ddf
Compare
renovate
Bot
force-pushed
the
renovate/go-golang.org-x-net-vulnerability
branch
from
March 30, 2026 22:11
3f11f71 to
c114ddf
Compare
renovate
Bot
force-pushed
the
renovate/go-golang.org-x-net-vulnerability
branch
from
March 30, 2026 22:11
c114ddf to
3f11f71
Compare
renovate
Bot
force-pushed
the
renovate/go-golang.org-x-net-vulnerability
branch
2 times, most recently
from
April 27, 2026 22:27
3f11f71 to
6251a95
Compare
renovate
Bot
force-pushed
the
renovate/go-golang.org-x-net-vulnerability
branch
2 times, most recently
from
June 12, 2026 22:34
6251a95 to
cc5350d
Compare
renovate
Bot
force-pushed
the
renovate/go-golang.org-x-net-vulnerability
branch
2 times, most recently
from
June 21, 2026 09:09
cc5350d to
5d9d972
Compare
renovate
Bot
force-pushed
the
renovate/go-golang.org-x-net-vulnerability
branch
from
July 2, 2026 10:41
5d9d972 to
bb6ee11
Compare
renovate
Bot
force-pushed
the
renovate/go-golang.org-x-net-vulnerability
branch
2 times, most recently
from
July 15, 2026 09:52
bb6ee11 to
b080462
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.15.0→v0.55.0HTTP/2 rapid reset can cause excessive work in net/http
CVE-2023-39325 / GHSA-4374-p667-p6c8
More information
Details
A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.
With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.
This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2.
The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
HTTP/2 Stream Cancellation Attack
CVE-2023-44487 / GHSA-qppj-fm5r-hxr3
More information
Details
HTTP/2 Rapid reset attack
The HTTP/2 protocol allows clients to indicate to the server that a previous stream should be canceled by sending a RST_STREAM frame. The protocol does not require the client and server to coordinate the cancellation in any way, the client may do it unilaterally. The client may also assume that the cancellation will take effect immediately when the server receives the RST_STREAM frame, before any other data from that TCP connection is processed.
Abuse of this feature is called a Rapid Reset attack because it relies on the ability for an endpoint to send a RST_STREAM frame immediately after sending a request frame, which makes the other endpoint start working and then rapidly resets the request. The request is canceled, but leaves the HTTP/2 connection open.
The HTTP/2 Rapid Reset attack built on this capability is simple: The client opens a large number of streams at once as in the standard HTTP/2 attack, but rather than waiting for a response to each request stream from the server or proxy, the client cancels each request immediately.
The ability to reset streams immediately allows each connection to have an indefinite number of requests in flight. By explicitly canceling the requests, the attacker never exceeds the limit on the number of concurrent open streams. The number of in-flight requests is no longer dependent on the round-trip time (RTT), but only on the available network bandwidth.
In a typical HTTP/2 server implementation, the server will still have to do significant amounts of work for canceled requests, such as allocating new stream data structures, parsing the query and doing header decompression, and mapping the URL to a resource. For reverse proxy implementations, the request may be proxied to the backend server before the RST_STREAM frame is processed. The client on the other hand paid almost no costs for sending the requests. This creates an exploitable cost asymmetry between the server and the client.
Multiple software artifacts implementing HTTP/2 are affected. This advisory was originally ingested from the
swift-nio-http2repo advisory and their original conent follows.swift-nio-http2 specific advisory
swift-nio-http2 is vulnerable to a denial-of-service vulnerability in which a malicious client can create and then reset a large number of HTTP/2 streams in a short period of time. This causes swift-nio-http2 to commit to a large amount of expensive work which it then throws away, including creating entirely new
Channels to serve the traffic. This can easily overwhelm anEventLoopand prevent it from making forward progress.swift-nio-http2 1.28 contains a remediation for this issue that applies reset counter using a sliding window. This constrains the number of stream resets that may occur in a given window of time. Clients violating this limit will have their connections torn down. This allows clients to continue to cancel streams for legitimate reasons, while constraining malicious actors.
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:AReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
net/http, x/net/http2: close connections when receiving too many headers
CVE-2023-45288 / GHSA-4v7x-pqxf-cx7m
More information
Details
An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames. Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed. This permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data, all associated with a request which is going to be rejected. These headers can include Huffman-encoded data which is significantly more expensive for the receiver to decode than for an attacker to send. The fix sets a limit on the amount of excess header frames we will process before closing a connection.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
HTTP Proxy bypass using IPv6 Zone IDs in golang.org/x/net
CVE-2025-22870 / GHSA-qxp5-gwg8-xv66
More information
Details
Matching of hosts against proxy patterns can improperly treat an IPv6 zone ID as a hostname component. For example, when the NO_PROXY environment variable is set to "*.example.com", a request to "[::1%25.example.com]:80` will incorrectly match and not be proxied.
Severity
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:LReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
golang.org/x/net vulnerable to Cross-site Scripting
CVE-2025-22872 / GHSA-vvgc-356p-c3xw
More information
Details
The tokenizer incorrectly interprets tags with unquoted attribute values that end with a solidus character (/) as self-closing. When directly using Tokenizer, this can result in such tags incorrectly being marked as self-closing, and when using the Parse functions, this can result in content following such tags as being placed in the wrong scope during DOM construction, but only when tags are in foreign content (e.g. , , etc contexts).
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Go Net HTML parser is vulnerable to denial of service
CVE-2026-25680 / GHSA-5cv4-jp36-h3mw
More information
Details
In Go Net (
golang.org/x/net) before verion 0.55.0, parsing arbitrary HTML can consume excessive CPU time, possibly leading to denial of service.Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:HReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.