Skip to content

Update module golang.org/x/net to v0.45.0 [SECURITY]#36

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/go-golang.org-x-net-vulnerability
Open

Update module golang.org/x/net to v0.45.0 [SECURITY]#36
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/go-golang.org-x-net-vulnerability

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate Bot commented Aug 7, 2024

This PR contains the following updates:

Package Change Age Confidence
golang.org/x/net v0.20.0v0.45.0 age confidence

net/http, x/net/http2: close connections when receiving too many headers

BIT-golang-2023-45288 / CVE-2023-45288 / GHSA-4v7x-pqxf-cx7m / GO-2024-2687

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 Score: 5.3 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


HTTP/2 CONTINUATION flood in net/http

BIT-golang-2023-45288 / CVE-2023-45288 / GHSA-4v7x-pqxf-cx7m / GO-2024-2687

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

Unknown

References

This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).


Non-linear parsing of case-insensitive content in golang.org/x/net/html

CVE-2024-45338 / GHSA-w32m-9786-jp63 / GO-2024-3333

More information

Details

An attacker can craft an input to the Parse functions that would be processed non-linearly with respect to its length, resulting in extremely slow parsing. This could cause a denial of service.

Severity

Unknown

References

This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).


HTTP Proxy bypass using IPv6 Zone IDs in golang.org/x/net

CVE-2025-22870 / GHSA-qxp5-gwg8-xv66 / GO-2025-3503

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 Score: 4.4 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L

References

This data is provided by OSV and 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 / GO-2025-3503

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

Unknown

References

This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).


golang.org/x/net vulnerable to Cross-site Scripting

CVE-2025-22872 / GHSA-vvgc-356p-c3xw / GO-2025-3595

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 Score: 5.3 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


Incorrect Neutralization of Input During Web Page Generation in x/net in golang.org/x/net

CVE-2025-22872 / GHSA-vvgc-356p-c3xw / GO-2025-3595

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

Unknown

References

This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).


Quadratic parsing complexity in golang.org/x/net/html

CVE-2025-47911 / GHSA-w4gw-w5jq-g9jh / GO-2026-4440

More information

Details

The html.Parse function in golang.org/x/net/html has quadratic parsing complexity when processing certain inputs, which can lead to denial of service (DoS) if an attacker provides specially crafted HTML content.

Severity

Unknown

References

This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).


Infinite parsing loop in golang.org/x/net

CVE-2025-58190 / GO-2026-4441

More information

Details

The html.Parse function in golang.org/x/net/html has an infinite parsing loop when processing certain inputs, which can lead to denial of service (DoS) if an attacker provides specially crafted HTML content.

Severity

Unknown

References

This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • ""
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the automated label Aug 7, 2024
@renovate
Copy link
Copy Markdown
Author

renovate Bot commented Aug 7, 2024

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 7 additional dependencies were updated
  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.20 -> 1.23.0
golang.org/x/crypto v0.18.0 -> v0.36.0
golang.org/x/mod v0.14.0 -> v0.17.0
golang.org/x/sync v0.6.0 -> v0.12.0
golang.org/x/sys v0.16.0 -> v0.31.0
golang.org/x/term v0.16.0 -> v0.30.0
golang.org/x/text v0.14.0 -> v0.23.0
golang.org/x/tools v0.17.0 -> v0.21.1-0.20240508182429-e35e4ccd0d2d

@renovate renovate Bot changed the title Update module golang.org/x/net to v0.23.0 [SECURITY] Update module golang.org/x/net to v0.33.0 [SECURITY] Dec 19, 2024
@renovate renovate Bot force-pushed the renovate/go-golang.org-x-net-vulnerability branch from f046538 to a2429ba Compare December 19, 2024 06:01
@renovate renovate Bot changed the title Update module golang.org/x/net to v0.33.0 [SECURITY] Update module golang.org/x/net to v0.36.0 [SECURITY] Mar 14, 2025
@renovate renovate Bot force-pushed the renovate/go-golang.org-x-net-vulnerability branch from a2429ba to 2771a2f Compare March 14, 2025 03:20
@renovate renovate Bot force-pushed the renovate/go-golang.org-x-net-vulnerability branch from 2771a2f to c9bfbc3 Compare April 8, 2025 23:45
@renovate renovate Bot changed the title Update module golang.org/x/net to v0.36.0 [SECURITY] Update module golang.org/x/net to v0.38.0 [SECURITY] Apr 19, 2025
@renovate renovate Bot force-pushed the renovate/go-golang.org-x-net-vulnerability branch from c9bfbc3 to d06965f Compare April 19, 2025 03:54
@renovate renovate Bot force-pushed the renovate/go-golang.org-x-net-vulnerability branch from d06965f to 98e1545 Compare May 9, 2025 23:48
@renovate renovate Bot force-pushed the renovate/go-golang.org-x-net-vulnerability branch 2 times, most recently from 6dfa2c7 to ad481fe Compare August 15, 2025 19:28
@renovate
Copy link
Copy Markdown
Author

renovate Bot commented Dec 17, 2025

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 7 additional dependencies were updated
  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.20 -> 1.24.0
golang.org/x/crypto v0.18.0 -> v0.42.0
golang.org/x/mod v0.14.0 -> v0.27.0
golang.org/x/sync v0.6.0 -> v0.17.0
golang.org/x/sys v0.16.0 -> v0.36.0
golang.org/x/term v0.16.0 -> v0.35.0
golang.org/x/text v0.14.0 -> v0.29.0
golang.org/x/tools v0.17.0 -> v0.36.0

@renovate renovate Bot changed the title Update module golang.org/x/net to v0.38.0 [SECURITY] Update module golang.org/x/net to v0.45.0 [SECURITY] Feb 7, 2026
@renovate renovate Bot force-pushed the renovate/go-golang.org-x-net-vulnerability branch from ad481fe to de793cd Compare February 7, 2026 03:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants