chore(deps): update go toolchain directive to v1.25.13 [security]

[felix-renovate]

This PR contains the following updates:

Package	Type	Update	Change
go (source)	toolchain	patch	1.25.10 → 1.25.13

---

Inefficient candidate hostname parsing in crypto/x509

BIT-golang-2026-27145 / CVE-2026-27145 / GO-2026-5037

More information

Details

(*x509.Certificate).VerifyHostname previously called matchHostnames in a loop over all DNS Subject Alternative Name (SAN) entries. This caused strings.Split(host, ".") to execute repeatedly on the same input hostname.

With a large DNS SAN list, verification costs scaled quadratically based on the number of SAN entries multiplied by the hostname's label count. Because x509.Verify validates hostnames before building the certificate chain, this overhead occurred even for untrusted certificates.

Severity

Unknown

References

• https://go.dev/cl/783621
• https://go.dev/issue/79694
• https://groups.google.com/g/golang-announce/c/tKs3rmcBcKw

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

---

Quadratic complexity in WordDecoder.DecodeHeader in mime

BIT-golang-2026-42504 / CVE-2026-42504 / GO-2026-5038

More information

Details

Decoding a maliciously-crafted MIME header containing many invalid encoded-words can consume excessive CPU.

Severity

Unknown

References

• https://go.dev/issue/79217
• https://go.dev/cl/774481
• https://groups.google.com/g/golang-announce/c/tKs3rmcBcKw

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

---

Arbitrary inputs are included in errors without any escaping in net/textproto

BIT-golang-2026-42507 / CVE-2026-42507 / GO-2026-5039

More information

Details

When returning errors, functions in the net/textproto package would include its input as part of the error. This might allow an attacker to inject misleading content to errors that are printed or logged.

Severity

Unknown

References

• https://go.dev/issue/79346
• https://go.dev/cl/777060
• https://groups.google.com/g/golang-announce/c/tKs3rmcBcKw

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

---

Root escape via symlink plus trailing slash in os

BIT-golang-2026-39822 / CVE-2026-39822 / GO-2026-4970

More information

Details

On Unix systems, opening a file in an os.Root improperly follows symlinks to locations outside of the Root when the final path component of the a path is a symbolic link and the path ends in /.

For example, 'root.Open("symlink/")' will open "symlink" even when "symlink" is a symbolic link pointing outside of the root.

Severity

Unknown

References

• https://go.dev/issue/79005
• https://groups.google.com/g/golang-announce/c/OrmQE_Yp5Sc
• https://go.dev/cl/797880

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

---

Invoking Encrypted Client Hello privacy leak in crypto/tls

BIT-golang-2026-42505 / CVE-2026-42505 / GO-2026-5856

More information

Details

Handshakes which used Encrypted Client Hello could be de-anonymized by a passive network observer due to a disclosure of pre-shared key identities in the unencrypted client hello.

Severity

Unknown

References

• https://go.dev/cl/775960
• https://go.dev/issue/79282
• https://groups.google.com/g/golang-announce/c/OrmQE_Yp5Sc

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

---

Invoking failure to reject ASCII-only Punycode-encoded labels in golang.org/x/net/idna

CVE-2026-39821 / GO-2026-5026

More information

Details

The ToASCII and ToUnicode functions incorrectly accept Punycode-encoded labels that decode to an ASCII-only label. For example, ToUnicode("xn--example-.com") incorrectly returns the name "example.com" rather than an error.

This behavior can lead to privilege escalation in programs using the idna package. For example, a program which performs privilege checks on the ASCII hostname may reject "example.com" but permit "xn--example-.com". If that program subsequently converts the ASCII hostname to Unicode, it will inadvertently permits access to the Unicode name "example.com".

Severity

Unknown

References

• https://go.dev/cl/767220
• https://go.dev/issue/78760
• https://groups.google.com/g/golang-announce/c/iI-mYSI0lu8
• https://groups.google.com/g/golang-announce/c/94pEornpRlI

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

---

Enforce maximum recursion depth in encoding/asn1

BIT-golang-2026-33818 / CVE-2026-33818 / GO-2026-5972

More information

Details

Enforce a recursion limit in Unmarshal to prevent stack exhaustion when parsing deeply-nested, recursive structures.

Severity

Unknown

References

• https://go.dev/issue/80405
• https://groups.google.com/g/golang-announce/c/94pEornpRlI
• https://go.dev/cl/814980

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

---

Add recursion depth guard during decode in encoding/xml

BIT-golang-2026-56859 / CVE-2026-56859 / GO-2026-6088

More information

Details

Previously, DecodeElement would reset the depth counter causing it to never fire; this could lead to stack exhaustion.

Severity

Unknown

References

• https://go.dev/issue/80481
• https://go.dev/cl/803320
• https://groups.google.com/g/golang-announce/c/94pEornpRlI

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

---

Apply ReadHeaderTimeout when doing unencrypted HTTP/2 check in net/http

BIT-golang-2026-56853 / CVE-2026-56853 / GO-2026-6089

More information

Details

When a server is configured to support unencrypted HTTP/2, it reads a few bytes from each new connection to see if they contain the HTTP/2 client preface. ReadHeaderTimeout is unexpectedly not being applied when doing this.

Severity

Unknown

References

• https://go.dev/issue/80205
• https://go.dev/cl/795540
• https://groups.google.com/g/golang-announce/c/94pEornpRlI

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

---

Limit handshake messages we are willing to accept post-handshake in crypto/tls

BIT-golang-2026-56862 / CVE-2026-56862 / GO-2026-6090

More information

Details

Handshake messages, such as KeyUpdate, are always considered as state-advancing, regardless of whether a handshake has been completed or not. As a result, a malicious client can keep sending KeyUpdate messages to force the server to keep performing key derivation operations indefinitely.

Severity

Unknown

References

• https://go.dev/issue/80528
• https://go.dev/cl/804261
• https://groups.google.com/g/golang-announce/c/94pEornpRlI

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

---

Fix Javascript regexp context tracking in html/template

BIT-golang-2026-56858 / CVE-2026-56858 / GO-2026-6091

More information

Details

Previously, pathological inputs could close an unescaped '/' early, allowing for attack-controlled data to inject arbitrary content, potentially leading to XSS.

Severity

Unknown

References

• https://go.dev/issue/80435
• https://go.dev/cl/807100
• https://groups.google.com/g/golang-announce/c/94pEornpRlI

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

---

Avoid quadratic complexity in resolvePath in net/url

BIT-golang-2026-56860 / CVE-2026-56860 / GO-2026-6218

More information

Details

Previously, resolving relative paths containing parent directory ('..') segments performed string conversions and buffer rewrites on each step, resulting in quadratic time complexity and high memory allocation overhead.

Now, path resolution operates on a byte buffer using index-based backtracking for '..' segments, eliminating the quadratic time complexity and significantly reducing memory allocations.

Severity

Unknown

References

• https://go.dev/cl/803681
• https://go.dev/issue/80494
• https://groups.google.com/g/golang-announce/c/94pEornpRlI

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

---

Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, 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 has been generated by Mend Renovate.