Skip to content

fix(security/unknown/lidia): update go toolchain directive to v1.25.13 [security] (release/v2.1) - #5515

Open
renovate-sh-app[bot] wants to merge 1 commit into
release/v2.1from
renovate/release/v2.1-security-lidia-go
Open

fix(security/unknown/lidia): update go toolchain directive to v1.25.13 [security] (release/v2.1)#5515
renovate-sh-app[bot] wants to merge 1 commit into
release/v2.1from
renovate/release/v2.1-security-lidia-go

Conversation

@renovate-sh-app

@renovate-sh-app renovate-sh-app Bot commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
go (source) toolchain patch 1.25.121.25.13

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

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


Enforce maximum recursion depth in encoding/asn1

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

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


Add recursion depth guard during decode in encoding/xml

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

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

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

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

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

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


Fix Javascript regexp context tracking in html/template

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

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


Avoid quadratic complexity in resolvePath in net/url

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

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

Need help?

You can ask for more help in the following Slack channel: #proj-renovate-self-hosted. In that channel you can also find ADR and FAQ docs in the Resources section.

…3 [security]

| datasource     | package | from    | to      |
| -------------- | ------- | ------- | ------- |
| golang-version | go      | 1.25.12 | 1.25.13 |


Signed-off-by: renovate-sh-app[bot] <219655108+renovate-sh-app[bot]@users.noreply.github.com>
Signed-off-by: renovate-sh-app[bot] <219655108+renovate-sh-app[bot]@users.noreply.github.com>
@renovate-sh-app
renovate-sh-app Bot force-pushed the renovate/release/v2.1-security-lidia-go branch from a660b7e to 41a010e Compare August 14, 2026 17:08
@renovate-sh-app renovate-sh-app Bot changed the title fix(security/unknown/lidia): update go toolchain directive to v1.26.6 [security] (release/v2.1) fix(security/unknown/lidia): update go toolchain directive to v1.25.13 [security] (release/v2.1) Aug 14, 2026
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