CVE-2025-47912

The Parse function permits values other than IPv6 addresses to be included in square brackets within the host component of a URL. RFC 3986 permits IPv6 addresses to be included within the host component, enclosed within square brackets. For example: "http://[::1]/". IPv4 addresses and hostnames must not appear within square brackets. Parse did not enforce this requirement.

The Parse function permits values other than IPv6 addresses to be included in square brackets within the host component of a URL. RFC 3986 permits IPv6 addresses to be included within the host component, enclosed within square brackets. For example: "http://[::1]/". IPv4 addresses and hostnames must not appear within square brackets. Parse did not enforce this requirement.

.

Security Fix(es):

The Parse function permits values other than IPv6 addresses to be included in square brackets within the host component of a URL. RFC 3986 permits IPv6 addresses to be included within the host component, enclosed within square brackets. For example: "http://[::1]/". IPv4 addresses and hostnames must not appear within square brackets. Parse did not enforce this requirement.(CVE-2025-47912)

In Go before 1.24.8 and 1.25.x before 1.25.2, Despite HTTP headers having a default limit of 1 MB, the number of cookies that can be parsed did not have a limit. By sending a lot of very small cookies such as "a=;", an attacker can make an HTTP server allocate a large amount of structs, causing large memory consumption.(CVE-2025-58186)

.

Security Fix(es):

The Parse function permits values other than IPv6 addresses to be included in square brackets within the host component of a URL. RFC 3986 permits IPv6 addresses to be included within the host component, enclosed within square brackets. For example: "http://[::1]/". IPv4 addresses and hostnames must not appear within square brackets. Parse did not enforce this requirement.(CVE-2025-47912)

In Go before 1.24.8 and 1.25.x before 1.25.2, Despite HTTP headers having a default limit of 1 MB, the number of cookies that can be parsed did not have a limit. By sending a lot of very small cookies such as "a=;", an attacker can make an HTTP server allocate a large amount of structs, causing large memory consumption.(CVE-2025-58186)

.

Security Fix(es):

The Parse function permits values other than IPv6 addresses to be included in square brackets within the host component of a URL. RFC 3986 permits IPv6 addresses to be included within the host component, enclosed within square brackets. For example: "http://[::1]/". IPv4 addresses and hostnames must not appear within square brackets. Parse did not enforce this requirement.(CVE-2025-47912)

Despite HTTP headers having a default limit of 1MB, the number of cookies that can be parsed does not have a limit. By sending a lot of very small cookies such as "a=;", an attacker can make an HTTP server allocate a large amount of structs, causing large memory consumption.(CVE-2025-58186)

.

Security Fix(es):

The Parse function permits values other than IPv6 addresses to be included in square brackets within the host component of a URL. RFC 3986 permits IPv6 addresses to be included within the host component, enclosed within square brackets. For example: "http://[::1]/". IPv4 addresses and hostnames must not appear within square brackets. Parse did not enforce this requirement.(CVE-2025-47912)

Despite HTTP headers having a default limit of 1MB, the number of cookies that can be parsed does not have a limit. By sending a lot of very small cookies such as "a=;", an attacker can make an HTTP server allocate a large amount of structs, causing large memory consumption.(CVE-2025-58186)

Within HostnameError.Error(), when constructing an error string, there is no limit to the number of hosts that will be printed out. Furthermore, the error string is constructed by repeated string concatenation, leading to quadratic runtime. Therefore, a certificate provided by a malicious actor can result in excessive resource consumption.(CVE-2025-61729)

.

Security Fix(es):

The Parse function permits values other than IPv6 addresses to be included in square brackets within the host component of a URL. RFC 3986 permits IPv6 addresses to be included within the host component, enclosed within square brackets. For example: "http://[::1]/". IPv4 addresses and hostnames must not appear within square brackets. Parse did not enforce this requirement.(CVE-2025-47912)

Despite HTTP headers having a default limit of 1MB, the number of cookies that can be parsed does not have a limit. By sending a lot of very small cookies such as "a=;", an attacker can make an HTTP server allocate a large amount of structs, causing large memory consumption.(CVE-2025-58186)

Due to the design of the name constraint checking algorithm, the processing time of some inputs scale non-linearly with respect to the size of the certificate. This affects programs which validate arbitrary certificate chains.(CVE-2025-58187)

The processing time for parsing some invalid inputs scales non-linearly with respect to the size of the input. This affects programs which parse untrusted PEM inputs.(CVE-2025-61723)

.

Security Fix(es):

The Parse function permits values other than IPv6 addresses to be included in square brackets within the host component of a URL. RFC 3986 permits IPv6 addresses to be included within the host component, enclosed within square brackets. For example: "http://[::1]/". IPv4 addresses and hostnames must not appear within square brackets. Parse did not enforce this requirement.(CVE-2025-47912)

Despite HTTP headers having a default limit of 1MB, the number of cookies that can be parsed does not have a limit. By sending a lot of very small cookies such as "a=;", an attacker can make an HTTP server allocate a large amount of structs, causing large memory consumption.(CVE-2025-58186)

crypto/x509: Exclude subdomain constraints do not restrict wildcard SANs Exclude subdomain constraints in certificate chains do not restrict the use of wildcard SANs in leaf certificates. For example, excluding the constraint on the subdomain test.example.com does not prevent the leaf certificate from claiming SAN*. example.com.(CVE-2025-61727)

Within HostnameError.Error(), when constructing an error string, there is no limit to the number of hosts that will be printed out. Furthermore, the error string is constructed by repeated string concatenation, leading to quadratic runtime. Therefore, a certificate provided by a malicious actor can result in excessive resource consumption.(CVE-2025-61729)

Git Large File Storage (LFS) replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server.

Security Fix(es):

The filepath.Walk and filepath.WalkDir functions are documented as not following symbolic links, but both functions are susceptible to a TOCTOU (time of check/time of use) race condition where a portion of the path being walked is replaced with a symbolic link while the walk is in progress.(CVE-2024-8244)

Gitk is a Tcl/Tk based Git history browser. Starting with 1.7.0, when a user clones an untrusted repository and runs gitk without additional command arguments, files for which the user has write permission can be created and truncated. The option Support per-file encoding must have been enabled before in Gitk's Preferences. This option is disabled by default. The same happens when Show origin of this line is used in the main window (regardless of whether Support per-file encoding is enabled or not). This vulnerability is fixed in 2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1, and 2.50.1.(CVE-2025-27613)

Proxy-Authorization and Proxy-Authenticate headers persisted on cross-origin redirects potentially leaking sensitive information.(CVE-2025-4673)

If the PATH environment variable contains paths which are executables (rather than just directories), passing certain strings to LookPath ("", ".", and ".."), can result in the binaries listed in the PATH being unexpectedly returned.(CVE-2025-47906)

When using http.CrossOriginProtection, the AddInsecureBypassPattern method can unexpectedly bypass more requests than intended. CrossOriginProtection then skips validation, but forwards the original request path, which may be served by a different handler without the intended security protections.(CVE-2025-47910)

The Parse function permits values other than IPv6 addresses to be included in square brackets within the host component of a URL. RFC 3986 permits IPv6 addresses to be included within the host component, enclosed within square brackets. For example: "http://[::1]/". IPv4 addresses and hostnames must not appear within square brackets. Parse did not enforce this requirement.(CVE-2025-47912)

SSH Agent servers do not validate the size of messages when processing new identity requests, which may cause the program to panic if the message is malformed due to an out of bounds read.(CVE-2025-47914)

Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. When cloning a repository Git knows to optionally fetch a bundle advertised by the remote server, which allows the server-side to offload parts of the clone to a CDN. The Git client does not perform sufficient validation of the advertised bundles, which allows the remote side to perform protocol injection. This protocol injection can cause the client to write the fetched bundle to a location controlled by the adversary. The fetched content is fully controlled by the server, which can in the worst case lead to arbitrary code execution. The use of bundle URIs is not enabled by default and can be controlled by the bundle.heuristic config option. Some cases of the vulnerability require that the adversary is in control of where a repository will be cloned to. This either requires social engineering or a recursive clone with submodules. These cases can thus be avoided by disabling recursive clones. This vulnerability is fixed in v2.43.7, v2.44.4, v2.45.4, v2.46.4, v2.47.3, v2.48.2, v2.49.1, and v2.50.1.(CVE-2025-48385)

SSH servers parsing GSSAPI authentication requests do not validate the number of mechanisms specified in the request, allowing an attacker to cause unbounded memory consumption.(CVE-2025-58181)

A vulnerability was found in Google Go up to 1.25.1 (Programming Language Software). It has been rated as…

Git Large File Storage (LFS) replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server.

Security Fix(es):

The filepath.Walk and filepath.WalkDir functions are documented as not following symbolic links, but both functions are susceptible to a TOCTOU (time of check/time of use) race condition where a portion of the path being walked is replaced with a symbolic link while the walk is in progress.(CVE-2024-8244)

Gitk is a Tcl/Tk based Git history browser. Starting with 1.7.0, when a user clones an untrusted repository and runs gitk without additional command arguments, files for which the user has write permission can be created and truncated. The option Support per-file encoding must have been enabled before in Gitk's Preferences. This option is disabled by default. The same happens when Show origin of this line is used in the main window (regardless of whether Support per-file encoding is enabled or not). This vulnerability is fixed in 2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1, and 2.50.1.(CVE-2025-27613)

Proxy-Authorization and Proxy-Authenticate headers persisted on cross-origin redirects potentially leaking sensitive information.(CVE-2025-4673)

If the PATH environment variable contains paths which are executables (rather than just directories), passing certain strings to LookPath ("", ".", and ".."), can result in the binaries listed in the PATH being unexpectedly returned.(CVE-2025-47906)

When using http.CrossOriginProtection, the AddInsecureBypassPattern method can unexpectedly bypass more requests than intended. CrossOriginProtection then skips validation, but forwards the original request path, which may be served by a different handler without the intended security protections.(CVE-2025-47910)

The Parse function permits values other than IPv6 addresses to be included in square brackets within the host component of a URL. RFC 3986 permits IPv6 addresses to be included within the host component, enclosed within square brackets. For example: "http://[::1]/". IPv4 addresses and hostnames must not appear within square brackets. Parse did not enforce this requirement.(CVE-2025-47912)

SSH Agent servers do not validate the size of messages when processing new identity requests, which may cause the program to panic if the message is malformed due to an out of bounds read.(CVE-2025-47914)

Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. When cloning a repository Git knows to optionally fetch a bundle advertised by the remote server, which allows the server-side to offload parts of the clone to a CDN. The Git client does not perform sufficient validation of the advertised bundles, which allows the remote side to perform protocol injection. This protocol injection can cause the client to write the fetched bundle to a location controlled by the adversary. The fetched content is fully controlled by the server, which can in the worst case lead to arbitrary code execution. The use of bundle URIs is not enabled by default and can be controlled by the bundle.heuristic config option. Some cases of the vulnerability require that the adversary is in control of where a repository will be cloned to. This either requires social engineering or a recursive clone with submodules. These cases can thus be avoided by disabling recursive clones. This vulnerability is fixed in v2.43.7, v2.44.4, v2.45.4, v2.46.4, v2.47.3, v2.48.2, v2.49.1, and v2.50.1.(CVE-2025-48385)

SSH servers parsing GSSAPI authentication requests do not validate the number of mechanisms specified in the request, allowing an attacker to cause unbounded memory consumption.(CVE-2025-58181)

A vulnerability was found in Google Go up to 1.25.1 (Programming Language Software). It has been rated as…

Git Large File Storage (LFS) replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server.

Security Fix(es):

Processing an incomplete post-handshake message for a QUIC connection can cause a panic.(CVE-2023-39321)

QUIC connections do not set an upper bound on the amount of data buffered when reading post-handshake messages, allowing a malicious QUIC connection to cause unbounded memory growth. With fix, connections now consistently reject messages larger than 65KiB in size.(CVE-2023-39322)

The filepath.Walk and filepath.WalkDir functions are documented as not following symbolic links, but both functions are susceptible to a TOCTOU (time of check/time of use) race condition where a portion of the path being walked is replaced with a symbolic link while the walk is in progress.(CVE-2024-8244)

Calling Verify with a VerifyOptions.KeyUsages that contains ExtKeyUsageAny unintentionally disabledpolicy validation. This only affected certificate chains which contain policy graphs, which are rather uncommon.(CVE-2025-22874)

Git LFS is a Git extension for versioning large files. In Git LFS versions 0.5.2 through 3.7.0, when populating a Git repository's working tree with the contents of Git LFS objects, certain Git LFS commands may write to files visible outside the current Git working tree if symbolic or hard links exist which collide with the paths of files tracked by Git LFS. The git lfs checkout and git lfs pull commands do not check for symbolic links before writing to files in the working tree, allowing an attacker to craft a repository containing symbolic or hard links that cause Git LFS to write to arbitrary file system locations accessible to the user running these commands. As well, when the git lfs checkout and git lfs pull commands are run in a bare repository, they could write to files visible outside the repository. The vulnerability is fixed in version 3.7.1. As a workaround, support for symlinks in Git may be disabled by setting the core.symlinks configuration option to false, after which further clones and fetches will not create symbolic links. However, any symbolic or hard links in existing repositories will still provide the opportunity for Git LFS to write to their targets.(CVE-2025-26625)

Gitk is a Tcl/Tk based Git history browser. Starting with 1.7.0, when a user clones an untrusted repository and runs gitk without additional command arguments, files for which the user has write permission can be created and truncated. The option Support per-file encoding must have been enabled before in Gitk's Preferences. This option is disabled by default. The same happens when Show origin of this line is used in the main window (regardless of whether Support per-file encoding is enabled or not). This vulnerability is fixed in 2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1, and 2.50.1.(CVE-2025-27613)

Gitk is a Tcl/Tk based Git history browser. Starting with 2.41.0, a Git repository can be crafted in such a way that with some social engineering a user who has cloned the repository can be tricked into running any script (e.g., Bourne shell, Perl, Python, ...) supplied by the attacker by invoking gitk filename, where filename has a particular structure. The script is run with the privileges of the user. This vulnerability is fixed in 2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1, and 2.50.(CVE-2025-27614)

Proxy-Authorization and Proxy-Authenticate headers persisted on cross-origin redirects potentially leaking sensitive information.(CVE-2025-4673)

The go command may execute unexpected commands when operating in untrusted VCS repositories. This occurs when possibly dangerous VCS configuration is present in repositories. This can happen when a repository was fetched via one VCS (e.g. Git), but contains metadata for another VCS (e.g. Mercurial). Modules which are retrieved using the go command line,…

The Parse function permits values other than IPv6 addresses to be included in square brackets within the host component of a URL. RFC 3986 permits IPv6 addresses to be included within the host component, enclosed within square brackets. For example: "http://[::1]/". IPv4 addresses and hostnames must not appear within square brackets. Parse did not enforce this requirement.

The Parse function permits values other than IPv6 addresses to be included in square brackets within the host component of a URL. RFC 3986 permits IPv6 addresses to be included within the host component, enclosed within square brackets. For example: "http://[::1]/". IPv4 addresses and hostnames must not appear within square brackets. Parse did not enforce this requirement.

The Parse function permits values other than IPv6 addresses to be included in square brackets within the host component of a URL. RFC 3986 permits IPv6 addresses to be included within the host component, enclosed within square brackets. For example: "http://[::1]/". IPv4 addresses and hostnames must not appear within square brackets. Parse did not enforce this requirement.

The Parse function permits values other than IPv6 addresses to be included in square brackets within the host component of a URL. RFC 3986 permits IPv6 addresses to be included within the host component, enclosed within square brackets. For example: "http://[::1]/". IPv4 addresses and hostnames must not appear within square brackets. Parse did not enforce this requirement.

The Parse function permits values other than IPv6 addresses to be included in square brackets within the host component of a URL. RFC 3986 permits IPv6 addresses to be included within the host component, enclosed within square brackets. For example: "http://[::1]/". IPv4 addresses and hostnames must not appear within square brackets. Parse did not enforce this requirement.

Insufficient validation of bracketed IPv6 hostnames in net/url. (CVE-2025-47912) Unbounded allocation when parsing GNU sparse map in archive/tar. (CVE-2025-58183) Parsing DER payload can cause memory exhaustion in encoding/asn1. (CVE-2025-58185) Lack of limit when parsing cookies can cause memory exhaustion in net/http. (CVE-2025-58186) Quadratic complexity when checking name constraints in crypto/x509. (CVE-2025-58187) Panic when validating certificates with DSA public keys in crypto/x509. (CVE-2025-58188) ALPN negotiation error contains attacker controlled information in crypto/tls. (CVE-2025-58189) Quadratic complexity when parsing some invalid inputs in encoding/pem. (CVE-2025-61723) Excessive CPU consumption in Reader.ReadResponse in net/textproto. (CVE-2025-61724) Excessive CPU consumption in ParseAddress in net/mail. (CVE-2025-61725) These packages fix the issues for the compiler only; applications using the functions still need to be rebuilt.

These are all security issues fixed in the go1.24-1.24.8-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the go1.25-1.25.2-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the govulncheck-vulndb-0.0.20251029T215107-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the kubecolor-0.5.3-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the regclient-0.10.0-1.1 package on the GA media of openSUSE Tumbleweed.

This update for go1.25 fixes the following issues:

Update to go1.25.5.

Security issues fixed:

• CVE-2025-61729: crypto/x509: excessive resource consumption in printing error string for host certificate validation (bsc#1254431).
• CVE-2025-61727: crypto/x509: excluded subdomain constraint doesn't preclude wildcard SAN (bsc#1254430).
• CVE-2025-61725: net/mail: excessive CPU consumption in ParseAddress (bsc#1251253).
• CVE-2025-61724: net/textproto: excessive CPU consumption in Reader.ReadResponse (bsc#1251262).
• CVE-2025-61723: encoding/pem: quadratic complexity when parsing some invalid inputs (bsc#1251256).
• CVE-2025-58189: crypto/tls: ALPN negotiation error contains attacker controlled information (bsc#1251255).
• CVE-2025-58188: crypto/x509: panic when validating certificates with DSA public keys (bsc#1251260).
• CVE-2025-58187: crypto/x509: quadratic complexity when checking name constraints (bsc#1251254).
• CVE-2025-58186: net/http: lack of limit when parsing cookies can cause memory exhaustion (bsc#1251259).
• CVE-2025-58185: encoding/asn1: pre-allocating memory when parsing DER payload can cause memory exhaustion (bsc#1251258).
• CVE-2025-58183: archive/tar: unbounded allocation when parsing GNU sparse map (bsc#1251261).
• CVE-2025-47912: net/url: insufficient validation of bracketed IPv6 hostnames (bsc#1251257).
• CVE-2025-47910: net/http: CrossOriginProtection insecure bypass patterns not limited to exact matches (bsc#1249141).

Other issues fixed and changes:

• Version 1.25.5:

  • go#76245 mime: FormatMediaType and ParseMediaType not compatible across 1.24 to 1.25
  • go#76360 os: on windows RemoveAll removing directories containing read-only files errors with unlinkat ... Access is denied, ReOpenFile error handling followup

• Version 1.25.4:

  • go#75480 cmd/link: linker panic and relocation errors with complex generics inlining
  • go#75775 runtime: build fails when run via QEMU for linux/amd64 running on linux/arm64
  • go#75790 crypto/internal/fips140/subtle: Go 1.25 subtle.xorBytes panic on MIPS
  • go#75832 net/url: ipv4 mapped ipv6 addresses should be valid in square brackets
  • go#75952 encoding/pem: regression when decoding blocks with leading garbage
  • go#75989 os: on windows RemoveAll removing directories containing read-only files errors with unlinkat ... Access is denied
  • go#76010 cmd/compile: any(func(){})==any(func(){}) does not panic but should
  • go#76029 pem/encoding: malformed line endings can cause panics

• Version 1.25.3:

  • go#75861 crypto/x509: TLS validation fails for FQDNs with trailing dot
  • go#75777 spec: Go1.25 spec should be dated closer to actual release date

• Version 1.25.2:

  • go#75111 os, syscall: volume handles with FILE_FLAG_OVERLAPPED fail when calling ReadAt
  • go#75116 os: Root.MkdirAll can return "file exists" when called concurrently on the same path
  • go#75139 os: Root.OpenRoot sets incorrect name, losing prefix of original root
  • go#75221 debug/pe: pe.Open fails on object files produced by llvm-mingw 21
  • go#75255 cmd/compile: export to DWARF types only referenced through interfaces
  • go#75347 testing/synctest: test timeout with no runnable goroutines
  • go#75357 net: new test TestIPv4WriteMsgUDPAddrPortTargetAddrIPVersion fails on plan9
  • go#75524 crypto/internal/fips140/rsa: requires a panic if self-tests fail
  • go#75537 context: Err can return non-nil before Done channel is closed
  • go#75539 net/http: internal error: connCount underflow
  • go#75595 cmd/compile: internal compiler error with GOEXPERIMENT=cgocheck2 on github.com/leodido/go-urn
  • go#75610 sync/atomic: comment for Uintptr.Or incorrectly describes return value
  • go#75669 runtime: debug.decoratemappings don't work as expected

• Version 1.25.1:

  • go#74822 cmd/go: "get toolchain@latest" should ignore release candidates
  • go#74999 net: WriteMsgUDPAddrPort should accept IPv4-mapped IPv6 destination addresses on IPv4 UDP sockets
  • go#75008 os/exec:…

This update for go1.24 fixes the following issues:

Update to go1.24.11.

Security issues fixed:

• CVE-2025-47912: net/url: insufficient validation of bracketed IPv6 hostnames (bsc#1251257).
• CVE-2025-58183: archive/tar: unbounded allocation when parsing GNU sparse map (bsc#1251261).
• CVE-2025-58185: encoding/asn1: pre-allocating memory when parsing DER payload can cause memory exhaustion (bsc#1251258).
• CVE-2025-58186: net/http: lack of limit when parsing cookies can cause memory exhaustion (bsc#1251259).
• CVE-2025-58187: crypto/x509: quadratic complexity when checking name constraints (bsc#1251254).
• CVE-2025-58188: crypto/x509: panic when validating certificates with DSA public keys (bsc#1251260).
• CVE-2025-58189: crypto/tls: ALPN negotiation error contains attacker controlled information (bsc#1251255).
• CVE-2025-61723: encoding/pem: quadratic complexity when parsing some invalid inputs (bsc#1251256).
• CVE-2025-61724: net/textproto: excessive CPU consumption in Reader.ReadResponse (bsc#1251262).
• CVE-2025-61725: net/mail: excessive CPU consumption in ParseAddress (bsc#1251253).
• CVE-2025-61727: crypto/x509: excluded subdomain constraint doesn't preclude wildcard SAN (bsc#1254430).
• CVE-2025-61729: crypto/x509: excessive resource consumption in printing error string for host certificate validation (bsc#1254431).

Other issues fixed and changes:

• Version 1.24.11:

  • go#76378 internal/cpu: incorrect CPU features bit parsing on loong64 cause illegal instruction core dumps on LA364 cores

• Version 1.24.10:

  • go#75831 net/url: ipv4 mapped ipv6 addresses should be valid in square brackets
  • go#75951 encoding/pem: regression when decoding blocks with leading garbage
  • go#76028 pem/encoding: malformed line endings can cause panics

• Version 1.24.9:

  • go#75860 crypto/x509: TLS validation fails for FQDNs with trailing dot

• Version 1.24.8:

  • go#75138 os: Root.OpenRoot sets incorrect name, losing prefix of original root
  • go#75220 debug/pe: pe.Open fails on object files produced by llvm-mingw 21
  • go#75351 cmd/link: panic on riscv64 with CGO enabled due to empty container symbol
  • go#75356 net: new test TestIPv4WriteMsgUDPAddrPortTargetAddrIPVersion fails on plan9
  • go#75359 os: new test TestOpenFileCreateExclDanglingSymlink fails on Plan 9
  • go#75523 crypto/internal/fips140/rsa: requires a panic if self-tests fail
  • go#75538 net/http: internal error: connCount underflow
  • go#75594 cmd/compile: internal compiler error with GOEXPERIMENT=cgocheck2 on github.com/leodido/go-urn
  • go#75609 sync/atomic: comment for Uintptr.Or incorrectly describes return value

• Version 1.24.7:

  • go#75007 os/exec: TestLookPath fails on plan9 after CL 685755
  • go#74821 cmd/go: "get toolchain@latest" should ignore release candidates
  • go#74818 net: WriteMsgUDPAddrPort should accept IPv4-mapped IPv6 destination addresses on IPv4 UDP sockets

• Packaging: migrate from update-alternatives to libalternatives (bsc#1245878).

• Package svgpan.js to fix issues with "go tool pprof" (bsc#1249985).

• Drop unused gccgo bootstrap code in go1.22+ (bsc#1248082).

This update for go1.25-openssl fixes the following issues:

• Update to version 1.25.7 (jsc#SLE-18320)
• CVE-2025-61730: crypto/tls: handshake messages may be processed at the incorrect encryption level (bsc#1256821)
• CVE-2025-68119: cmd/go: unexpected code execution when invoking toolchain (bsc#1256820)
• CVE-2025-61731: cmd/go: bypass of flag sanitization can lead to arbitrary code execution (bsc#1256819)
• CVE-2025-61726: net/http: memory exhaustion in Request.ParseForm (bsc#1256817)
• CVE-2025-61728: archive/zip: denial of service when parsing arbitrary ZIP archives (bsc#1256816)
• CVE-2025-68121: crypto/tls: Config.Clone copies automatically generated session ticket keys, session resumption does not account for the expiration of full certificate chain (bsc#1256818)
• CVE-2025-61729: crypto/x509: excessive resource consumption in printing error string for host certificate validation (bsc#1254431)
• CVE-2025-61727: crypto/x509: excluded subdomain constraint doesn't preclude wildcard SA (bsc#1254430)
• CVE-2025-58189: crypto/tls: ALPN negotiation error contains attacker controlled information (bsc#1251255)
• CVE-2025-61725: net/mail: excessive CPU consumption in ParseAddress (bsc#1251253)
• CVE-2025-58188: crypto/x509: panic when validating certificates with DSA public keys (bsc#1251260)
• CVE-2025-58185: encoding/asn1: pre-allocating memory when parsing DER payload can cause memory exhaustion (bsc#1251258)
• CVE-2025-58186: net/http: lack of limit when parsing cookies can cause memory exhaustion (bsc#1251259)
• CVE-2025-61723: encoding/pem: quadratic complexity when parsing some invalid inputs (bsc#1251256)
• CVE-2025-58183: archive/tar: unbounded allocation when parsing GNU sparse map (bsc#1251261)
• CVE-2025-47912: net/url: insufficient validation of bracketed IPv6 hostnames (bsc#1251257)
• CVE-2025-58187: crypto/x509: quadratic complexity when checking name constraints (bsc#1251254)
• CVE-2025-61724: net/textproto: excessive CPU consumption in Reader.ReadResponse (bsc#1251262)

This update for go1.24-openssl fixes the following issues:

• Update to version 1.24.13 (jsc#SLE-18320)
• CVE-2025-58189: crypto/tls: ALPN negotiation error contains attacker controlled information. (bsc#1251255)
• CVE-2025-61725: net/mail: excessive CPU consumption in ParseAddress. (bsc#1251253)
• CVE-2025-58188: crypto/x509: panic when validating certificates with DSA public keys. (bsc#1251260)
• CVE-2025-58185: encoding/asn1: pre-allocating memory when parsing DER payload can cause memory exhaustion. (bsc#1251258)
• CVE-2025-58186: net/http: lack of limit when parsing cookies can cause memory exhaustion. (bsc#1251259)
• CVE-2025-61723: encoding/pem: quadratic complexity when parsing some invalid inputs. (bsc#1251256)
• CVE-2025-58183: archive/tar: unbounded allocation when parsing GNU sparse map. (bsc#1251261)
• CVE-2025-47912: net/url: insufficient validation of bracketed IPv6 hostnames. (bsc#1251257)
• CVE-2025-58187: crypto/x509: quadratic complexity when checking name constraints. (bsc#1251254)
• CVE-2025-61724: net/textproto: excessive CPU consumption in Reader.ReadResponse. (bsc#1251262)
• CVE-2025-61729: crypto/x509: excessive resource consumption in printing error string for host certificate validation. (bsc#1254431)
• CVE-2025-61727: crypto/x509: excluded subdomain constraint doesn't preclude wildcard SAN. (bsc#1254430)
• CVE-2025-61730: crypto/tls: handshake messages may be processed at the incorrect encryption level. (bsc#1256821)
• CVE-2025-61731: cmd/go: bypass of flag sanitization can lead to arbitrary code execution. (bsc#1256819)
• CVE-2025-61726: net/http: memory exhaustion in Request.ParseForm. (bsc#1256817)
• CVE-2025-61728: archive/zip: denial of service when parsing arbitrary ZIP archives. (bsc#1256816)
• CVE-2025-68121: crypto/tls: Config.Clone copies automatically generated session ticket keys, session resumption does not account for the expiration of full certificate chain. (bsc#1256818)
• CVE-2025-61732: cmd/go: potential code smuggling using doc comments. (bsc#1257692)
• CVE-2025-68119: cmd/go: unexpected code execution when invoking toolchain. (bsc#1256820)

This update for govulncheck-vulndb fixes the following issues:

• Update to version 0.0.20260723T184607 2026-07-23T18:46:07Z (jsc#PED-11136).

Go CVE Numbering Authority IDs added or updated with aliases:

• GO-2026-4730 CVE-2026-33022 GHSA-cv4x-93xx-wgfj
• GO-2026-4761 CVE-2026-33211 GHSA-j5q5-j9gm-2w5c
• GO-2026-5102 CVE-2026-45021 GHSA-3vcp-chfh-f6r2
• GO-2026-5272 CVE-2026-40938 GHSA-94jr-7pqp-xhcq
• GO-2026-5486 CVE-2026-40924 GHSA-m2cx-gpqf-qf74
• GO-2026-5542 CVE-2026-40090 GHSA-pj97-4p9w-gx3q
• GO-2026-5630 CVE-2026-25542 GHSA-rmx9-2pp3-xhcr
• GO-2026-5643 CVE-2026-40923 GHSA-rx35-6rhx-7858
• GO-2026-5675 CVE-2026-41492 GHSA-vvf7-6rmr-m29q
• GO-2026-5711 CVE-2026-40161 GHSA-wjxp-xrpv-xpff
• GO-2026-5746 CVE-2026-41567 GHSA-x86f-5xw2-fm2r
• GO-2026-5749 CVE-2026-41328 GHSA-x92x-px7w-4gx4
• GO-2026-5837 CVE-2026-44840 GHSA-q2m9-6jp9-c6mc
• GO-2026-5929 CVE-2026-44342 GHSA-26v7-h57m-gh9m
• GO-2026-5930 CVE-2026-33655 GHSA-6qcr-qxgr-m7fv
• GO-2026-5933 GHSA-3g4q-2f67-2gvh
• GO-2026-5934 GHSA-59qp-cfj3-rp64
• GO-2026-5935 GHSA-7856-g3gv-9wq8
• GO-2026-5936 CVE-2026-53552 GHSA-26rh-24rg-j3vv
• GO-2026-5937 CVE-2026-53508 GHSA-2jcc-mxv7-p3f9
• GO-2026-5938 CVE-2026-53553 GHSA-4g5x-hcwm-82jw
• GO-2026-5939 CVE-2026-10517 GHSA-698x-9w2p-7vvp
• GO-2026-5940 CVE-2026-53572 GHSA-6w3m-4hhp-775q
• GO-2026-5941 CVE-2026-53487 GHSA-gvhc-wv3v-7pf8
• GO-2026-5942 CVE-2026-46600
• GO-2026-5944 CVE-2026-50197 GHSA-659f-rgp5-w4wf
• GO-2026-5945 CVE-2026-6815 GHSA-rmxx-v9rj-vpvg
• GO-2026-5946 CVE-2026-52831 GHSA-v5px-423j-pf7p
• GO-2026-5947 CVE-2026-53649 GHSA-xqhv-chqm-fhcc
• GO-2026-5948 CVE-2026-50554 GHSA-588f-fvcv-xhvf
• GO-2026-5949 CVE-2026-50553 GHSA-rqrh-8wpv-x7hh
• GO-2026-5950 CVE-2026-53602 GHSA-339v-266x-79xr
• GO-2026-5951 CVE-2026-10219 GHSA-6jm8-4fhr-5w64
• GO-2026-5952 CVE-2026-49834 GHSA-9vcr-p3rj-q5q6
• GO-2026-5953 CVE-2026-9094 GHSA-c9w5-qp6m-m395
• GO-2026-5956 CVE-2026-55252 GHSA-h5g6-xmh4-hc37
• GO-2026-5957 CVE-2026-54158 GHSA-5xfx-xj4h-5p7r
• GO-2026-5958 CVE-2026-54068 GHSA-gcm7-57gf-953c
• GO-2026-5959 CVE-2026-54072 GHSA-h29v-hj44-q8cv
• GO-2026-5961 CVE-2026-54069 GHSA-hvr9-72v2-fff3
• GO-2026-5962 CVE-2026-54088 GHSA-m93h-4hw7-5qcm
• GO-2026-5963 CVE-2026-54067 GHSA-mvjr-vv3c-w4qv
• GO-2026-5964 CVE-2026-54066 GHSA-p4m3-mgmm-c664
• GO-2026-5965 CVE-2026-54070 GHSA-w7cg-whh7-xp28
• GO-2026-5966 CVE-2026-54089 GHSA-xqp3-jq6g-x3qm
• GO-2026-5967 CVE-2026-50551 GHSA-56mp-4f3v-fgj2
• GO-2026-5968 CVE-2026-54174 GHSA-fpg8-7664-jc5q
• GO-2026-5969 GHSA-g936-7jqj-mwv8
• GO-2026-5970 CVE-2026-56852
• GO-2026-5973 CVE-2026-54250 GHSA-jxr7-mqhw-9p98
• GO-2026-5974 CVE-2026-44300 GHSA-wmj8-9953-vff5
• GO-2026-5975 CVE-2026-50018 GHSA-42j2-w334-qxw7
• GO-2026-5976 CVE-2026-50141 GHSA-g7mm-9vx7-jm7h
• GO-2026-5977 CVE-2026-50013 GHSA-qrh4-p6v4-mrfg
• GO-2026-5978 CVE-2026-50125 GHSA-qw5r-ppcg-f8rj
• GO-2026-5979 CVE-2026-50006 GHSA-xrcf-6jh3-ggvx
• GO-2026-5980 CVE-2026-50158 GHSA-2c7f-fxww-6w6c
• GO-2026-5981 GHSA-mqxv-9rm6-w8qc
• GO-2026-5982 GHSA-pqg7-v6wh-3pfp
• GO-2026-5984 CVE-2026-53604 GHSA-2p2f-px33-4vv5
• GO-2026-5985 GHSA-7rx3-5wx3-5v76
• GO-2026-5986 CVE-2026-61699 GHSA-cm26-5974-52h8
• GO-2026-5987 CVE-2026-55513 GHSA-g4x6-jcvr-9m3g
• GO-2026-5988 CVE-2026-54628 GHSA-hwrq-8wxh-q4xv
• GO-2026-5989 CVE-2026-55512 GHSA-m3cx-mwpg-32jg
• GO-2026-5990 CVE-2026-54629 GHSA-mf78-3rpf-r784
• GO-2026-5991 CVE-2026-53603 GHSA-q4vm-pq3q-8wgq
• GO-2026-5992 CVE-2026-61549 GHSA-qf34-295c-26v8
• GO-2026-5996 CVE-2026-54450 GHSA-pph6-vfjv-vpjw
• GO-2026-5997 CVE-2026-54452 GHSA-xgch-x3mx-cm3c
• GO-2026-5998 CVE-2026-54495 GHSA-398h-7f66-3h4p
• GO-2026-5999 CVE-2026-10814 GHSA-jh6h-v6mp-h22v
• GO-2026-6002 CVE-2026-58196 GHSA-pr64-jmmf-jp54
• GO-2026-6003 CVE-2026-53714 GHSA-22xc-xg2r-9j7v
• GO-2026-6004 CVE-2026-52833 GHSA-3v79-m2cg-89ww
• GO-2026-6005 CVE-2026-53715 GHSA-8fv2-88gg-hm7q
• GO-2026-6006 CVE-2026-53716 GHSA-cxpq-8v7q-cg56 *…

Root has patched CVE-2025-47912 in the golang-1.24 package for Root:Debian:13. Multiple fixed versions available.

This update for go1.25 fixes the following issues:

go1.25.2 (released 2025-10-07) includes security fixes to the archive/tar, crypto/tls, crypto/x509, encoding/asn1, encoding/pem, net/http, net/mail, net/textproto, and net/url packages, as well as bug fixes to the compiler, the runtime, and the context, debug/pe, net/http, os, and sync/atomic packages. (bsc#1244485)

CVE-2025-58189 CVE-2025-61725 CVE-2025-58188 CVE-2025-58185 CVE-2025-58186 CVE-2025-61723 CVE-2025-58183 CVE-2025-47912 CVE-2025-58187 CVE-2025-61724:

• bsc#1251255 CVE-2025-58189: crypto/tls: ALPN negotiation error contains attacker controlled information

• bsc#1251253 CVE-2025-61725: net/mail: excessive CPU consumption in ParseAddress

• bsc#1251260 CVE-2025-58188: crypto/x509: panic when validating certificates with DSA public keys

• bsc#1251258 CVE-2025-58185: encoding/asn1: pre-allocating memory when parsing DER payload can cause memory exhaustion

• bsc#1251259 CVE-2025-58186: net/http: lack of limit when parsing cookies can cause memory exhaustion

• bsc#1251256 CVE-2025-61723: encoding/pem: quadratic complexity when parsing some invalid inputs

• bsc#1251261 CVE-2025-58183: archive/tar: unbounded allocation when parsing GNU sparse map

• bsc#1251257 CVE-2025-47912: net/url: insufficient validation of bracketed IPv6 hostnames

• bsc#1251254 CVE-2025-58187: crypto/x509: quadratic complexity when checking name constraints

• bsc#1251262 CVE-2025-61724: net/textproto: excessive CPU consumption in Reader.ReadResponse

• go#75111 os, syscall: volume handles with FILE_FLAG_OVERLAPPED fail when calling ReadAt

• go#75116 os: Root.MkdirAll can return 'file exists' when called concurrently on the same path

• go#75139 os: Root.OpenRoot sets incorrect name, losing prefix of original root

• go#75221 debug/pe: pe.Open fails on object files produced by llvm-mingw 21

• go#75255 cmd/compile: export to DWARF types only referenced through interfaces

• go#75347 testing/synctest: test timeout with no runnable goroutines

• go#75357 net: new test TestIPv4WriteMsgUDPAddrPortTargetAddrIPVersion fails on plan9

• go#75524 crypto/internal/fips140/rsa: requires a panic if self-tests fail

• go#75537 context: Err can return non-nil before Done channel is closed

• go#75539 net/http: internal error: connCount underflow

• go#75595 cmd/compile: internal compiler error with GOEXPERIMENT=cgocheck2 on github.com/leodido/go-urn

• go#75610 sync/atomic: comment for Uintptr.Or incorrectly describes return value

• go#75669 runtime: debug.decoratemappings don't work as expected

This update for go1.25 fixes the following issues:

Update to go1.25.5.

Security issues fixed:

• CVE-2025-61729: crypto/x509: excessive resource consumption in printing error string for host certificate validation (bsc#1254431).
• CVE-2025-61727: crypto/x509: excluded subdomain constraint doesn't preclude wildcard SAN (bsc#1254430).
• CVE-2025-61725: net/mail: excessive CPU consumption in ParseAddress (bsc#1251253).
• CVE-2025-61724: net/textproto: excessive CPU consumption in Reader.ReadResponse (bsc#1251262).
• CVE-2025-61723: encoding/pem: quadratic complexity when parsing some invalid inputs (bsc#1251256).
• CVE-2025-58189: crypto/tls: ALPN negotiation error contains attacker controlled information (bsc#1251255).
• CVE-2025-58188: crypto/x509: panic when validating certificates with DSA public keys (bsc#1251260).
• CVE-2025-58187: crypto/x509: quadratic complexity when checking name constraints (bsc#1251254).
• CVE-2025-58186: net/http: lack of limit when parsing cookies can cause memory exhaustion (bsc#1251259).
• CVE-2025-58185: encoding/asn1: pre-allocating memory when parsing DER payload can cause memory exhaustion (bsc#1251258).
• CVE-2025-58183: archive/tar: unbounded allocation when parsing GNU sparse map (bsc#1251261).
• CVE-2025-47912: net/url: insufficient validation of bracketed IPv6 hostnames (bsc#1251257).
• CVE-2025-47910: net/http: CrossOriginProtection insecure bypass patterns not limited to exact matches (bsc#1249141).

Other issues fixed and changes:

• Version 1.25.5:

  • go#76245 mime: FormatMediaType and ParseMediaType not compatible across 1.24 to 1.25
  • go#76360 os: on windows RemoveAll removing directories containing read-only files errors with unlinkat ... Access is denied, ReOpenFile error handling followup

• Version 1.25.4:

  • go#75480 cmd/link: linker panic and relocation errors with complex generics inlining
  • go#75775 runtime: build fails when run via QEMU for linux/amd64 running on linux/arm64
  • go#75790 crypto/internal/fips140/subtle: Go 1.25 subtle.xorBytes panic on MIPS
  • go#75832 net/url: ipv4 mapped ipv6 addresses should be valid in square brackets
  • go#75952 encoding/pem: regression when decoding blocks with leading garbage
  • go#75989 os: on windows RemoveAll removing directories containing read-only files errors with unlinkat ... Access is denied
  • go#76010 cmd/compile: any(func(){})==any(func(){}) does not panic but should
  • go#76029 pem/encoding: malformed line endings can cause panics

• Version 1.25.3:

  • go#75861 crypto/x509: TLS validation fails for FQDNs with trailing dot
  • go#75777 spec: Go1.25 spec should be dated closer to actual release date

• Version 1.25.2:

  • go#75111 os, syscall: volume handles with FILE_FLAG_OVERLAPPED fail when calling ReadAt
  • go#75116 os: Root.MkdirAll can return "file exists" when called concurrently on the same path
  • go#75139 os: Root.OpenRoot sets incorrect name, losing prefix of original root
  • go#75221 debug/pe: pe.Open fails on object files produced by llvm-mingw 21
  • go#75255 cmd/compile: export to DWARF types only referenced through interfaces
  • go#75347 testing/synctest: test timeout with no runnable goroutines
  • go#75357 net: new test TestIPv4WriteMsgUDPAddrPortTargetAddrIPVersion fails on plan9
  • go#75524 crypto/internal/fips140/rsa: requires a panic if self-tests fail
  • go#75537 context: Err can return non-nil before Done channel is closed
  • go#75539 net/http: internal error: connCount underflow
  • go#75595 cmd/compile: internal compiler error with GOEXPERIMENT=cgocheck2 on github.com/leodido/go-urn
  • go#75610 sync/atomic: comment for Uintptr.Or incorrectly describes return value
  • go#75669 runtime: debug.decoratemappings don't work as expected

• Version 1.25.1:

  • go#74822 cmd/go: "get toolchain@latest" should ignore release candidates
  • go#74999 net: WriteMsgUDPAddrPort should accept IPv4-mapped IPv6 destination addresses on IPv4 UDP sockets
  • go#75008 os/exec:…

This update for go1.24 fixes the following issues:

Update to go1.24.11.

Security issues fixed:

• CVE-2025-47912: net/url: insufficient validation of bracketed IPv6 hostnames (bsc#1251257).
• CVE-2025-58183: archive/tar: unbounded allocation when parsing GNU sparse map (bsc#1251261).
• CVE-2025-58185: encoding/asn1: pre-allocating memory when parsing DER payload can cause memory exhaustion (bsc#1251258).
• CVE-2025-58186: net/http: lack of limit when parsing cookies can cause memory exhaustion (bsc#1251259).
• CVE-2025-58187: crypto/x509: quadratic complexity when checking name constraints (bsc#1251254).
• CVE-2025-58188: crypto/x509: panic when validating certificates with DSA public keys (bsc#1251260).
• CVE-2025-58189: crypto/tls: ALPN negotiation error contains attacker controlled information (bsc#1251255).
• CVE-2025-61723: encoding/pem: quadratic complexity when parsing some invalid inputs (bsc#1251256).
• CVE-2025-61724: net/textproto: excessive CPU consumption in Reader.ReadResponse (bsc#1251262).
• CVE-2025-61725: net/mail: excessive CPU consumption in ParseAddress (bsc#1251253).
• CVE-2025-61727: crypto/x509: excluded subdomain constraint doesn't preclude wildcard SAN (bsc#1254430).
• CVE-2025-61729: crypto/x509: excessive resource consumption in printing error string for host certificate validation (bsc#1254431).

Other issues fixed and changes:

• Version 1.24.11:

  • go#76378 internal/cpu: incorrect CPU features bit parsing on loong64 cause illegal instruction core dumps on LA364 cores

• Version 1.24.10:

  • go#75831 net/url: ipv4 mapped ipv6 addresses should be valid in square brackets
  • go#75951 encoding/pem: regression when decoding blocks with leading garbage
  • go#76028 pem/encoding: malformed line endings can cause panics

• Version 1.24.9:

  • go#75860 crypto/x509: TLS validation fails for FQDNs with trailing dot

• Version 1.24.8:

  • go#75138 os: Root.OpenRoot sets incorrect name, losing prefix of original root
  • go#75220 debug/pe: pe.Open fails on object files produced by llvm-mingw 21
  • go#75351 cmd/link: panic on riscv64 with CGO enabled due to empty container symbol
  • go#75356 net: new test TestIPv4WriteMsgUDPAddrPortTargetAddrIPVersion fails on plan9
  • go#75359 os: new test TestOpenFileCreateExclDanglingSymlink fails on Plan 9
  • go#75523 crypto/internal/fips140/rsa: requires a panic if self-tests fail
  • go#75538 net/http: internal error: connCount underflow
  • go#75594 cmd/compile: internal compiler error with GOEXPERIMENT=cgocheck2 on github.com/leodido/go-urn
  • go#75609 sync/atomic: comment for Uintptr.Or incorrectly describes return value

• Version 1.24.7:

  • go#75007 os/exec: TestLookPath fails on plan9 after CL 685755
  • go#74821 cmd/go: "get toolchain@latest" should ignore release candidates
  • go#74818 net: WriteMsgUDPAddrPort should accept IPv4-mapped IPv6 destination addresses on IPv4 UDP sockets

• Packaging: migrate from update-alternatives to libalternatives (bsc#1245878).

• Package svgpan.js to fix issues with "go tool pprof" (bsc#1249985).

• Drop unused gccgo bootstrap code in go1.22+ (bsc#1248082).

This update for go1.24 fixes the following issues:

go1.24.9 (released 2025-10-13) includes fixes to the crypto/x509 package. (bsc#1236217)

• crypto/x509: TLS validation fails for FQDNs with trailing dot

go1.24.8 (released 2025-10-07) includes security fixes to the archive/tar, crypto/tls, crypto/x509, encoding/asn1, encoding/pem, net/http, net/mail, net/textproto, and net/url packages, as well as bug fixes to the compiler, the linker, and the debug/pe, net/http, os, and sync/atomic packages. (bsc#1236217)

CVE-2025-58189 CVE-2025-61725 CVE-2025-58188 CVE-2025-58185 CVE-2025-58186 CVE-2025-61723 CVE-2025-58183 CVE-2025-47912 CVE-2025-58187 CVE-2025-61724:

• bsc#1251255 CVE-2025-58189: crypto/tls: ALPN negotiation error contains attacker controlled information
• bsc#1251253 CVE-2025-61725: net/mail: excessive CPU consumption in ParseAddress
• bsc#1251260 CVE-2025-58188: crypto/x509: panic when validating certificates with DSA public keys
• bsc#1251258 CVE-2025-58185: encoding/asn1: pre-allocating memory when parsing DER payload can cause memory exhaustion
• bsc#1251259 CVE-2025-58186: net/http: lack of limit when parsing cookies can cause memory exhaustion
• bsc#1251256 CVE-2025-61723: encoding/pem: quadratic complexity when parsing some invalid inputs
• bsc#1251261 CVE-2025-58183: archive/tar: unbounded allocation when parsing GNU sparse map
• bsc#1251257 CVE-2025-47912: net/url: insufficient validation of bracketed IPv6 hostnames
• bsc#1251254 CVE-2025-58187: crypto/x509: quadratic complexity when checking name constraints
• bsc#1251262 CVE-2025-61724: net/textproto: excessive CPU consumption in Reader.ReadResponse
• os: Root.OpenRoot sets incorrect name, losing prefix of original root
• debug/pe: pe.Open fails on object files produced by llvm-mingw 21
• cmd/link: panic on riscv64 with CGO enabled due to empty container symbol
• net: new test TestIPv4WriteMsgUDPAddrPortTargetAddrIPVersion fails on plan9
• os: new test TestOpenFileCreateExclDanglingSymlink fails on Plan 9
• crypto/internal/fips140/rsa: requires a panic if self-tests fail
• net/http: internal error: connCount underflow
• cmd/compile: internal compiler error with GOEXPERIMENT=cgocheck2 on github.com/leodido/go-urn
• sync/atomic: comment for Uintptr.Or incorrectly describes return value

This update for go1.24-openssl fixes the following issues:

Update to version 1.24.12 (released 2026-01-15) (jsc#SLE-18320, bsc#1236217):

Security fixes:

• CVE-2025-47912: net/url: insufficient validation of bracketed IPv6 hostnames (bsc#1251257).
• CVE-2025-58183: archive/tar: unbounded allocation when parsing GNU sparse map (bsc#1251261).
• CVE-2025-58185: encoding/asn1: pre-allocating memory when parsing DER payload can cause memory exhaustion (bsc#1251258).
• CVE-2025-58186: net/http: lack of limit when parsing cookies can cause memory exhaustion (bsc#1251259).
• CVE-2025-58187: crypto/x509: quadratic complexity when checking name constraints (bsc#1251254).
• CVE-2025-58188: crypto/x509: panic when validating certificates with DSA public keys (bsc#1251260).
• CVE-2025-58189: crypto/tls: ALPN negotiation error contains attacker controlled information (bsc#1251255).
• CVE-2025-61723: encoding/pem: quadratic complexity when parsing some invalid inputs (bsc#1251256).
• CVE-2025-61724: net/textproto: excessive CPU consumption in Reader.ReadResponse (bsc#1251262).
• CVE-2025-61725: net/mail: excessive CPU consumption in ParseAddress (bsc#1251253).
• CVE-2025-61726: net/http: memory exhaustion in Request.ParseForm (bsc#1256817).
• CVE-2025-61727: crypto/x509: excluded subdomain constraint doesn't preclude wildcard SAN (bsc#1254430).
• CVE-2025-61728: archive/zip: denial of service when parsing arbitrary ZIP archives (bsc#1256816).
• CVE-2025-61729: crypto/x509: excessive resource consumption in printing error string for host certificate validation (bsc#1254431).
• CVE-2025-61730: crypto/tls: handshake messages may be processed at the incorrect encryption level (bsc#1256821).
• CVE-2025-61731: cmd/go: bypass of flag sanitization can lead to arbitrary code execution (bsc#1256819).
• CVE-2025-68119: cmd/go: unexpected code execution when invoking toolchain (bsc#1256820).
• CVE-2025-68121: crypto/tls: Config.Clone copies automatically generated session ticket keys, session resumption does not account for the expiration of full certificate chain (bsc#1256818).

Other fixes:

• go#74818 net: WriteMsgUDPAddrPort should accept IPv4-mapped IPv6 destination addresses on IPv4 UDP sockets
• go#74821 cmd/go: 'get toolchain@latest' should ignore release candidates
• go#75007 os/exec: TestLookPath fails on plan9 after CL 685755
• go#75138 os: Root.OpenRoot sets incorrect name, losing prefix of original root
• go#75220 debug/pe: pe.Open fails on object files produced by llvm-mingw 21
• go#75351 cmd/link: panic on riscv64 with CGO enabled due to empty container symbol
• go#75356 net: new test TestIPv4WriteMsgUDPAddrPortTargetAddrIPVersion fails on plan9
• go#75359 os: new test TestOpenFileCreateExclDanglingSymlink fails on Plan 9
• go#75523 crypto/internal/fips140/rsa: requires a panic if self-tests fail
• go#75538 net/http: internal error: connCount underflow
• go#75594 cmd/compile: internal compiler error with GOEXPERIMENT=cgocheck2 on github.com/leodido/go-urn
• go#75609 sync/atomic: comment for Uintptr.Or incorrectly describes return value
• go#75831 net/url: ipv4 mapped ipv6 addresses should be valid in square brackets
• go#75860 crypto/x509: TLS validation fails for FQDNs with trailing dot
• go#75951 encoding/pem: regression when decoding blocks with leading garbage
• go#76028 pem/encoding: malformed line endings can cause panics
• go#76378 internal/cpu: incorrect CPU features bit parsing on loong64 cause illegal instruction core dumps on LA364 cores
• go#76408 crypto/tls: earlyTrafficSecret should use ClientHelloInner if ECH enabled
• go#76624 os: on Unix, Readdirnames skips directory entries with zero inodes
• go#76760 runtime: stack split at bad time in os/signal with Go 1.25.4 windows 386
• go#76796 runtime: race detector crash on ppc64le
• go#76966 cmd/compile/internal/ssa: Compile.func1(): panic during sccp while compiling <function>: runtime error: index out of…

This update for go1.25-openssl fixes the following issues:

Update to version 1.25.6 (released 2026-01-15) (jsc#SLE-18320, bsc#1244485):

Security fixes:

• CVE-2025-4674 cmd/go: disable support for multiple vcs in one module (bsc#1246118).
• CVE-2025-47906 os/exec: LookPath bug: incorrect expansion of '', '.' and '..' in some PATH configurations (bsc#1247719).
• CVE-2025-47907 database/sql: incorrect results returned from Rows.Scan (bsc#1247720).
• CVE-2025-47910 net/http: CrossOriginProtection insecure bypass patterns not limited to exact matches (bsc#1249141).
• CVE-2025-47912 net/url: insufficient validation of bracketed IPv6 hostnames (bsc#1251257).
• CVE-2025-58183 archive/tar: unbounded allocation when parsing GNU sparse map (bsc#1251261).
• CVE-2025-58185 encoding/asn1: pre-allocating memory when parsing DER payload can cause memory exhaustion (bsc#1251258).
• CVE-2025-58186 net/http: lack of limit when parsing cookies can cause memory exhaustion (bsc#1251259).
• CVE-2025-58187 crypto/x509: quadratic complexity when checking name constraints (bsc#1251254).
• CVE-2025-58188 crypto/x509: panic when validating certificates with DSA public keys (bsc#1251260).
• CVE-2025-58189 crypto/tls: ALPN negotiation error contains attacker controlled information (bsc#1251255).
• CVE-2025-61723 encoding/pem: quadratic complexity when parsing some invalid inputs (bsc#1251256).
• CVE-2025-61724 net/textproto: excessive CPU consumption in Reader.ReadResponse (bsc#1251262).
• CVE-2025-61725 net/mail: excessive CPU consumption in ParseAddress (bsc#1251253).
• CVE-2025-61726 net/http: memory exhaustion in Request.ParseForm (bsc#1256817).
• CVE-2025-61727 crypto/x509: excluded subdomain constraint doesn't preclude wildcard SAN (bsc#1254430).
• CVE-2025-61728 archive/zip: denial of service when parsing arbitrary ZIP archives (bsc#1256816).
• CVE-2025-61729 crypto/x509: excessive resource consumption in printing error string for host certificate validation (bsc#1254431).
• CVE-2025-61730 crypto/tls: handshake messages may be processed at the incorrect encryption level (bsc#1256821).
• CVE-2025-61731 cmd/go: bypass of flag sanitization can lead to arbitrary code execution (bsc#1256819).
• CVE-2025-68119 cmd/go: unexpected code execution when invoking toolchain (bsc#1256820).
• CVE-2025-68121 crypto/tls: Config.Clone copies automatically generated session ticket keys, session resumption does not account for the expiration of full certificate chain (bsc#1256818).

Other fixes:

• go#74822 cmd/go: 'get toolchain@latest' should ignore release candidates
• go#74999 net: WriteMsgUDPAddrPort should accept IPv4-mapped IPv6 destination addresses on IPv4 UDP sockets
• go#75008 os/exec: TestLookPath fails on plan9 after CL 685755
• go#75021 testing/synctest: bubble not terminating
• go#75083 os: File.Seek doesn't set the correct offset with Windows overlapped handles
• go#75111 os, syscall: volume handles with FILE_FLAG_OVERLAPPED fail when calling ReadAt
• go#75116 os: Root.MkdirAll can return 'file exists' when called concurrently on the same path
• go#75139 os: Root.OpenRoot sets incorrect name, losing prefix of original root
• go#75221 debug/pe: pe.Open fails on object files produced by llvm-mingw 21
• go#75255 cmd/compile: export to DWARF types only referenced through interfaces
• go#75347 testing/synctest: test timeout with no runnable goroutines
• go#75357 net: new test TestIPv4WriteMsgUDPAddrPortTargetAddrIPVersion fails on plan9
• go#75480 cmd/link: linker panic and relocation errors with complex generics inlining
• go#75524 crypto/internal/fips140/rsa: requires a panic if self-tests fail
• go#75537 context: Err can return non-nil before Done channel is closed
• go#75539 net/http: internal error: connCount underflow
• go#75595 cmd/compile: internal compiler error with GOEXPERIMENT=cgocheck2 on github.com/leodido/go-urn
• go#75610 sync/atomic: comment for Uintptr.Or incorrectly describes…

This update for go1.25-openssl fixes the following issues:

Update to version 1.25.6 (released 2026-01-15) (jsc#SLE-18320, bsc#1244485):

Security fixes:

• CVE-2025-4674 cmd/go: disable support for multiple vcs in one module (bsc#1246118).
• CVE-2025-47906 os/exec: LookPath bug: incorrect expansion of '', '.' and '..' in some PATH configurations (bsc#1247719).
• CVE-2025-47907 database/sql: incorrect results returned from Rows.Scan (bsc#1247720).
• CVE-2025-47910 net/http: CrossOriginProtection insecure bypass patterns not limited to exact matches (bsc#1249141).
• CVE-2025-47912 net/url: insufficient validation of bracketed IPv6 hostnames (bsc#1251257).
• CVE-2025-58183 archive/tar: unbounded allocation when parsing GNU sparse map (bsc#1251261).
• CVE-2025-58185 encoding/asn1: pre-allocating memory when parsing DER payload can cause memory exhaustion (bsc#1251258).
• CVE-2025-58186 net/http: lack of limit when parsing cookies can cause memory exhaustion (bsc#1251259).
• CVE-2025-58187 crypto/x509: quadratic complexity when checking name constraints (bsc#1251254).
• CVE-2025-58188 crypto/x509: panic when validating certificates with DSA public keys (bsc#1251260).
• CVE-2025-58189 crypto/tls: ALPN negotiation error contains attacker controlled information (bsc#1251255).
• CVE-2025-61723 encoding/pem: quadratic complexity when parsing some invalid inputs (bsc#1251256).
• CVE-2025-61724 net/textproto: excessive CPU consumption in Reader.ReadResponse (bsc#1251262).
• CVE-2025-61725 net/mail: excessive CPU consumption in ParseAddress (bsc#1251253).
• CVE-2025-61726 net/http: memory exhaustion in Request.ParseForm (bsc#1256817).
• CVE-2025-61727 crypto/x509: excluded subdomain constraint doesn't preclude wildcard SAN (bsc#1254430).
• CVE-2025-61728 archive/zip: denial of service when parsing arbitrary ZIP archives (bsc#1256816).
• CVE-2025-61729 crypto/x509: excessive resource consumption in printing error string for host certificate validation (bsc#1254431).
• CVE-2025-61730 crypto/tls: handshake messages may be processed at the incorrect encryption level (bsc#1256821).
• CVE-2025-61731 cmd/go: bypass of flag sanitization can lead to arbitrary code execution (bsc#1256819).
• CVE-2025-68119 cmd/go: unexpected code execution when invoking toolchain (bsc#1256820).
• CVE-2025-68121 crypto/tls: Config.Clone copies automatically generated session ticket keys, session resumption does not account for the expiration of full certificate chain (bsc#1256818).

Other fixes:

• go#74822 cmd/go: 'get toolchain@latest' should ignore release candidates
• go#74999 net: WriteMsgUDPAddrPort should accept IPv4-mapped IPv6 destination addresses on IPv4 UDP sockets
• go#75008 os/exec: TestLookPath fails on plan9 after CL 685755
• go#75021 testing/synctest: bubble not terminating
• go#75083 os: File.Seek doesn't set the correct offset with Windows overlapped handles
• go#75111 os, syscall: volume handles with FILE_FLAG_OVERLAPPED fail when calling ReadAt
• go#75116 os: Root.MkdirAll can return 'file exists' when called concurrently on the same path
• go#75139 os: Root.OpenRoot sets incorrect name, losing prefix of original root
• go#75221 debug/pe: pe.Open fails on object files produced by llvm-mingw 21
• go#75255 cmd/compile: export to DWARF types only referenced through interfaces
• go#75347 testing/synctest: test timeout with no runnable goroutines
• go#75357 net: new test TestIPv4WriteMsgUDPAddrPortTargetAddrIPVersion fails on plan9
• go#75480 cmd/link: linker panic and relocation errors with complex generics inlining
• go#75524 crypto/internal/fips140/rsa: requires a panic if self-tests fail
• go#75537 context: Err can return non-nil before Done channel is closed
• go#75539 net/http: internal error: connCount underflow
• go#75595 cmd/compile: internal compiler error with GOEXPERIMENT=cgocheck2 on github.com/leodido/go-urn
• go#75610 sync/atomic: comment for Uintptr.Or incorrectly describes…

This update for go1.24-openssl fixes the following issues:

Update to version 1.24.12 (released 2026-01-15) (jsc#SLE-18320, bsc#1236217):

Security fixes:

• CVE-2025-47912: net/url: insufficient validation of bracketed IPv6 hostnames (bsc#1251257).
• CVE-2025-58183: archive/tar: unbounded allocation when parsing GNU sparse map (bsc#1251261).
• CVE-2025-58185: encoding/asn1: pre-allocating memory when parsing DER payload can cause memory exhaustion (bsc#1251258).
• CVE-2025-58186: net/http: lack of limit when parsing cookies can cause memory exhaustion (bsc#1251259).
• CVE-2025-58187: crypto/x509: quadratic complexity when checking name constraints (bsc#1251254).
• CVE-2025-58188: crypto/x509: panic when validating certificates with DSA public keys (bsc#1251260).
• CVE-2025-58189: crypto/tls: ALPN negotiation error contains attacker controlled information (bsc#1251255).
• CVE-2025-61723: encoding/pem: quadratic complexity when parsing some invalid inputs (bsc#1251256).
• CVE-2025-61724: net/textproto: excessive CPU consumption in Reader.ReadResponse (bsc#1251262).
• CVE-2025-61725: net/mail: excessive CPU consumption in ParseAddress (bsc#1251253).
• CVE-2025-61726: net/http: memory exhaustion in Request.ParseForm (bsc#1256817).
• CVE-2025-61727: crypto/x509: excluded subdomain constraint doesn't preclude wildcard SAN (bsc#1254430).
• CVE-2025-61728: archive/zip: denial of service when parsing arbitrary ZIP archives (bsc#1256816).
• CVE-2025-61729: crypto/x509: excessive resource consumption in printing error string for host certificate validation (bsc#1254431).
• CVE-2025-61730: crypto/tls: handshake messages may be processed at the incorrect encryption level (bsc#1256821).
• CVE-2025-61731: cmd/go: bypass of flag sanitization can lead to arbitrary code execution (bsc#1256819).
• CVE-2025-68119: cmd/go: unexpected code execution when invoking toolchain (bsc#1256820).
• CVE-2025-68121: crypto/tls: Config.Clone copies automatically generated session ticket keys, session resumption does not account for the expiration of full certificate chain (bsc#1256818).

Other fixes:

• go#74818 net: WriteMsgUDPAddrPort should accept IPv4-mapped IPv6 destination addresses on IPv4 UDP sockets
• go#74821 cmd/go: 'get toolchain@latest' should ignore release candidates
• go#75007 os/exec: TestLookPath fails on plan9 after CL 685755
• go#75138 os: Root.OpenRoot sets incorrect name, losing prefix of original root
• go#75220 debug/pe: pe.Open fails on object files produced by llvm-mingw 21
• go#75351 cmd/link: panic on riscv64 with CGO enabled due to empty container symbol
• go#75356 net: new test TestIPv4WriteMsgUDPAddrPortTargetAddrIPVersion fails on plan9
• go#75359 os: new test TestOpenFileCreateExclDanglingSymlink fails on Plan 9
• go#75523 crypto/internal/fips140/rsa: requires a panic if self-tests fail
• go#75538 net/http: internal error: connCount underflow
• go#75594 cmd/compile: internal compiler error with GOEXPERIMENT=cgocheck2 on github.com/leodido/go-urn
• go#75609 sync/atomic: comment for Uintptr.Or incorrectly describes return value
• go#75831 net/url: ipv4 mapped ipv6 addresses should be valid in square brackets
• go#75860 crypto/x509: TLS validation fails for FQDNs with trailing dot
• go#75951 encoding/pem: regression when decoding blocks with leading garbage
• go#76028 pem/encoding: malformed line endings can cause panics
• go#76378 internal/cpu: incorrect CPU features bit parsing on loong64 cause illegal instruction core dumps on LA364 cores
• go#76408 crypto/tls: earlyTrafficSecret should use ClientHelloInner if ECH enabled
• go#76624 os: on Unix, Readdirnames skips directory entries with zero inodes
• go#76760 runtime: stack split at bad time in os/signal with Go 1.25.4 windows 386
• go#76796 runtime: race detector crash on ppc64le
• go#76966 cmd/compile/internal/ssa: Compile.func1(): panic during sccp while compiling <function>: runtime error: index out of…

This update for go1.25-openssl fixes the following issues:

• Update to version 1.25.7 (jsc#SLE-18320)
• CVE-2025-61730: crypto/tls: handshake messages may be processed at the incorrect encryption level (bsc#1256821)
• CVE-2025-68119: cmd/go: unexpected code execution when invoking toolchain (bsc#1256820)
• CVE-2025-61731: cmd/go: bypass of flag sanitization can lead to arbitrary code execution (bsc#1256819)
• CVE-2025-61726: net/http: memory exhaustion in Request.ParseForm (bsc#1256817)
• CVE-2025-61728: archive/zip: denial of service when parsing arbitrary ZIP archives (bsc#1256816)
• CVE-2025-68121: crypto/tls: Config.Clone copies automatically generated session ticket keys, session resumption does not account for the expiration of full certificate chain (bsc#1256818)
• CVE-2025-61729: crypto/x509: excessive resource consumption in printing error string for host certificate validation (bsc#1254431)
• CVE-2025-61727: crypto/x509: excluded subdomain constraint doesn't preclude wildcard SA (bsc#1254430)
• CVE-2025-58189: crypto/tls: ALPN negotiation error contains attacker controlled information (bsc#1251255)
• CVE-2025-61725: net/mail: excessive CPU consumption in ParseAddress (bsc#1251253)
• CVE-2025-58188: crypto/x509: panic when validating certificates with DSA public keys (bsc#1251260)
• CVE-2025-58185: encoding/asn1: pre-allocating memory when parsing DER payload can cause memory exhaustion (bsc#1251258)
• CVE-2025-58186: net/http: lack of limit when parsing cookies can cause memory exhaustion (bsc#1251259)
• CVE-2025-61723: encoding/pem: quadratic complexity when parsing some invalid inputs (bsc#1251256)
• CVE-2025-58183: archive/tar: unbounded allocation when parsing GNU sparse map (bsc#1251261)
• CVE-2025-47912: net/url: insufficient validation of bracketed IPv6 hostnames (bsc#1251257)
• CVE-2025-58187: crypto/x509: quadratic complexity when checking name constraints (bsc#1251254)
• CVE-2025-61724: net/textproto: excessive CPU consumption in Reader.ReadResponse (bsc#1251262)

This update for go1.24-openssl fixes the following issues:

• Update to version 1.24.13 (jsc#SLE-18320)
• CVE-2025-58189: crypto/tls: ALPN negotiation error contains attacker controlled information. (bsc#1251255)
• CVE-2025-61725: net/mail: excessive CPU consumption in ParseAddress. (bsc#1251253)
• CVE-2025-58188: crypto/x509: panic when validating certificates with DSA public keys. (bsc#1251260)
• CVE-2025-58185: encoding/asn1: pre-allocating memory when parsing DER payload can cause memory exhaustion. (bsc#1251258)
• CVE-2025-58186: net/http: lack of limit when parsing cookies can cause memory exhaustion. (bsc#1251259)
• CVE-2025-61723: encoding/pem: quadratic complexity when parsing some invalid inputs. (bsc#1251256)
• CVE-2025-58183: archive/tar: unbounded allocation when parsing GNU sparse map. (bsc#1251261)
• CVE-2025-47912: net/url: insufficient validation of bracketed IPv6 hostnames. (bsc#1251257)
• CVE-2025-58187: crypto/x509: quadratic complexity when checking name constraints. (bsc#1251254)
• CVE-2025-61724: net/textproto: excessive CPU consumption in Reader.ReadResponse. (bsc#1251262)
• CVE-2025-61729: crypto/x509: excessive resource consumption in printing error string for host certificate validation. (bsc#1254431)
• CVE-2025-61727: crypto/x509: excluded subdomain constraint doesn't preclude wildcard SAN. (bsc#1254430)
• CVE-2025-61730: crypto/tls: handshake messages may be processed at the incorrect encryption level. (bsc#1256821)
• CVE-2025-61731: cmd/go: bypass of flag sanitization can lead to arbitrary code execution. (bsc#1256819)
• CVE-2025-61726: net/http: memory exhaustion in Request.ParseForm. (bsc#1256817)
• CVE-2025-61728: archive/zip: denial of service when parsing arbitrary ZIP archives. (bsc#1256816)
• CVE-2025-68121: crypto/tls: Config.Clone copies automatically generated session ticket keys, session resumption does not account for the expiration of full certificate chain. (bsc#1256818)
• CVE-2025-61732: cmd/go: potential code smuggling using doc comments. (bsc#1257692)
• CVE-2025-68119: cmd/go: unexpected code execution when invoking toolchain. (bsc#1256820)