CVE-2025-61732

A discrepancy between how Go and C/C++ comments were parsed allowed for code smuggling into the resulting cgo binary.

A discrepancy between how Go and C/C++ comments were parsed allowed for code smuggling into the resulting cgo binary.

The Go Programming Language.

Security Fix(es):

The net/url package does not set a limit on the number of query parameters in a query. While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.(CVE-2025-61726)

archive/zip uses a super-linear file name indexing algorithm that is invoked the first time a file in an archive is opened. This can lead to a denial of service when consuming a maliciously constructed ZIP archive.(CVE-2025-61728)

Building a malicious file with cmd/go can cause can cause a write to an attacker-controlled file with partial control of the file content. The "#cgo pkg-config:" directive in a Go source file provides command-line arguments to provide to the Go pkg-config command. An attacker can provide a "--log-file" argument to this directive, causing pkg-config to write to an attacker-controlled location.(CVE-2025-61731)

A discrepancy between how Go and C/C++ comments were parsed allowed for code smuggling into the resulting cgo binary.(CVE-2025-61732)

Downloading and building modules with malicious version strings can cause local code execution. On systems with Mercurial (hg) installed, downloading modules from non-standard sources (e.g., custom domains) can cause unexpected code execution due to how external VCS commands are constructed. This issue can also be triggered by providing a malicious version string to the toolchain. On systems with Git installed, downloading and building modules with malicious version strings can allow an attacker to write to arbitrary files on the filesystem. This can only be triggered by explicitly providing the malicious version strings to the toolchain and does not affect usage of @latest or bare module paths.(CVE-2025-68119)

During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.(CVE-2025-68121)

The Go Programming Language.

Security Fix(es):

The net/url package does not set a limit on the number of query parameters in a query. While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.(CVE-2025-61726)

archive/zip uses a super-linear file name indexing algorithm that is invoked the first time a file in an archive is opened. This can lead to a denial of service when consuming a maliciously constructed ZIP archive.(CVE-2025-61728)

Building a malicious file with cmd/go can cause can cause a write to an attacker-controlled file with partial control of the file content. The "#cgo pkg-config:" directive in a Go source file provides command-line arguments to provide to the Go pkg-config command. An attacker can provide a "--log-file" argument to this directive, causing pkg-config to write to an attacker-controlled location.(CVE-2025-61731)

A discrepancy between how Go and C/C++ comments were parsed allowed for code smuggling into the resulting cgo binary.(CVE-2025-61732)

Downloading and building modules with malicious version strings can cause local code execution. On systems with Mercurial (hg) installed, downloading modules from non-standard sources (e.g., custom domains) can cause unexpected code execution due to how external VCS commands are constructed. This issue can also be triggered by providing a malicious version string to the toolchain. On systems with Git installed, downloading and building modules with malicious version strings can allow an attacker to write to arbitrary files on the filesystem. This can only be triggered by explicitly providing the malicious version strings to the toolchain and does not affect usage of @latest or bare module paths.(CVE-2025-68119)

During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.(CVE-2025-68121)

The Go Programming Language.

Security Fix(es):

The net/url package does not set a limit on the number of query parameters in a query. While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.(CVE-2025-61726)

Building a malicious file with cmd/go can cause can cause a write to an attacker-controlled file with partial control of the file content. The "#cgo pkg-config:" directive in a Go source file provides command-line arguments to provide to the Go pkg-config command. An attacker can provide a "--log-file" argument to this directive, causing pkg-config to write to an attacker-controlled location.(CVE-2025-61731)

A discrepancy between how Go and C/C++ comments were parsed allowed for code smuggling into the resulting cgo binary.(CVE-2025-61732)

Downloading and building modules with malicious version strings can cause local code execution. On systems with Mercurial (hg) installed, downloading modules from non-standard sources (e.g., custom domains) can cause unexpected code execution due to how external VCS commands are constructed. This issue can also be triggered by providing a malicious version string to the toolchain. On systems with Git installed, downloading and building modules with malicious version strings can allow an attacker to write to arbitrary files on the filesystem. This can only be triggered by explicitly providing the malicious version strings to the toolchain and does not affect usage of @latest or bare module paths.(CVE-2025-68119)

During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.(CVE-2025-68121)

The Go Programming Language.

Security Fix(es):

The net/url package does not set a limit on the number of query parameters in a query. While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.(CVE-2025-61726)

archive/zip uses a super-linear file name indexing algorithm that is invoked the first time a file in an archive is opened. This can lead to a denial of service when consuming a maliciously constructed ZIP archive.(CVE-2025-61728)

Building a malicious file with cmd/go can cause can cause a write to an attacker-controlled file with partial control of the file content. The "#cgo pkg-config:" directive in a Go source file provides command-line arguments to provide to the Go pkg-config command. An attacker can provide a "--log-file" argument to this directive, causing pkg-config to write to an attacker-controlled location.(CVE-2025-61731)

A discrepancy between how Go and C/C++ comments were parsed allowed for code smuggling into the resulting cgo binary.(CVE-2025-61732)

Downloading and building modules with malicious version strings can cause local code execution. On systems with Mercurial (hg) installed, downloading modules from non-standard sources (e.g., custom domains) can cause unexpected code execution due to how external VCS commands are constructed. This issue can also be triggered by providing a malicious version string to the toolchain. On systems with Git installed, downloading and building modules with malicious version strings can allow an attacker to write to arbitrary files on the filesystem. This can only be triggered by explicitly providing the malicious version strings to the toolchain and does not affect usage of @latest or bare module paths.(CVE-2025-68119)

During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.(CVE-2025-68121)

The Go Programming Language.

Security Fix(es):

The net/url package does not set a limit on the number of query parameters in a query. While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.(CVE-2025-61726)

archive/zip uses a super-linear file name indexing algorithm that is invoked the first time a file in an archive is opened. This can lead to a denial of service when consuming a maliciously constructed ZIP archive.(CVE-2025-61728)

Building a malicious file with cmd/go can cause can cause a write to an attacker-controlled file with partial control of the file content. The "#cgo pkg-config:" directive in a Go source file provides command-line arguments to provide to the Go pkg-config command. An attacker can provide a "--log-file" argument to this directive, causing pkg-config to write to an attacker-controlled location.(CVE-2025-61731)

A discrepancy between how Go and C/C++ comments were parsed allowed for code smuggling into the resulting cgo binary.(CVE-2025-61732)

Downloading and building modules with malicious version strings can cause local code execution. On systems with Mercurial (hg) installed, downloading modules from non-standard sources (e.g., custom domains) can cause unexpected code execution due to how external VCS commands are constructed. This issue can also be triggered by providing a malicious version string to the toolchain. On systems with Git installed, downloading and building modules with malicious version strings can allow an attacker to write to arbitrary files on the filesystem. This can only be triggered by explicitly providing the malicious version strings to the toolchain and does not affect usage of @latest or bare module paths.(CVE-2025-68119)

During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.(CVE-2025-68121)

The Go Programming Language.

Security Fix(es):

The net/url package does not set a limit on the number of query parameters in a query. While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.(CVE-2025-61726)

archive/zip uses a super-linear file name indexing algorithm that is invoked the first time a file in an archive is opened. This can lead to a denial of service when consuming a maliciously constructed ZIP archive.(CVE-2025-61728)

Building a malicious file with cmd/go can cause can cause a write to an attacker-controlled file with partial control of the file content. The "#cgo pkg-config:" directive in a Go source file provides command-line arguments to provide to the Go pkg-config command. An attacker can provide a "--log-file" argument to this directive, causing pkg-config to write to an attacker-controlled location.(CVE-2025-61731)

A discrepancy between how Go and C/C++ comments were parsed allowed for code smuggling into the resulting cgo binary.(CVE-2025-61732)

Downloading and building modules with malicious version strings can cause local code execution. On systems with Mercurial (hg) installed, downloading modules from non-standard sources (e.g., custom domains) can cause unexpected code execution due to how external VCS commands are constructed. This issue can also be triggered by providing a malicious version string to the toolchain. On systems with Git installed, downloading and building modules with malicious version strings can allow an attacker to write to arbitrary files on the filesystem. This can only be triggered by explicitly providing the malicious version strings to the toolchain and does not affect usage of @latest or bare module paths.(CVE-2025-68119)

During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.(CVE-2025-68121)

The golang packages provide the Go programming language compiler.

Security Fix(es):

• golang: archive/zip: Excessive CPU consumption when building archive index in archive/zip (CVE-2025-61728)

• golang: net/url: Memory exhaustion in query parameter parsing in net/url (CVE-2025-61726)

• cmd/cgo: Potential code smuggling via doc comments in cmd/cgo (CVE-2025-61732)

• crypto/tls: Unexpected session resumption in crypto/tls (CVE-2025-68121)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Go Toolset provides the Go programming language tools and libraries. Go is alternatively known as golang.

Security Fix(es):

• golang: archive/zip: Excessive CPU consumption when building archive index in archive/zip (CVE-2025-61728)

• golang: net/url: Memory exhaustion in query parameter parsing in net/url (CVE-2025-61726)

• cmd/cgo: Potential code smuggling via doc comments in cmd/cgo (CVE-2025-61732)

• crypto/tls: Unexpected session resumption in crypto/tls (CVE-2025-68121)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The golang packages provide the Go programming language compiler.

Security Fix(es):

• golang: archive/zip: Excessive CPU consumption when building archive index in archive/zip (CVE-2025-61728)

• golang: net/url: Memory exhaustion in query parameter parsing in net/url (CVE-2025-61726)

• cmd/cgo: Potential code smuggling via doc comments in cmd/cgo (CVE-2025-61732)

• crypto/tls: Unexpected session resumption in crypto/tls (CVE-2025-68121)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

A discrepancy between how Go and C/C++ comments were parsed allowed for code smuggling into the resulting cgo binary.

The golang packages provide the Go programming language compiler.

Security Fix(es):

• golang: archive/zip: Excessive CPU consumption when building archive index in archive/zip (CVE-2025-61728)
• golang: net/url: Memory exhaustion in query parameter parsing in net/url (CVE-2025-61726)
• cmd/cgo: Potential code smuggling via doc comments in cmd/cgo (CVE-2025-61732)
• crypto/tls: Unexpected session resumption in crypto/tls (CVE-2025-68121)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Go Toolset provides the Go programming language tools and libraries. Go is alternatively known as golang.

Security Fix(es):

• golang: archive/zip: Excessive CPU consumption when building archive index in archive/zip (CVE-2025-61728)
• golang: net/url: Memory exhaustion in query parameter parsing in net/url (CVE-2025-61726)
• cmd/cgo: Potential code smuggling via doc comments in cmd/cgo (CVE-2025-61732)
• crypto/tls: Unexpected session resumption in crypto/tls (CVE-2025-68121)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The golang packages provide the Go programming language compiler.

Security Fix(es):

• golang: archive/zip: Excessive CPU consumption when building archive index in archive/zip (CVE-2025-61728)
• golang: net/url: Memory exhaustion in query parameter parsing in net/url (CVE-2025-61726)
• cmd/cgo: Potential code smuggling via doc comments in cmd/cgo (CVE-2025-61732)
• crypto/tls: Unexpected session resumption in crypto/tls (CVE-2025-68121)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

A discrepancy between how Go and C/C++ comments were parsed allowed for code smuggling into the resulting cgo binary.

A discrepancy between how Go and C/C++ comments were parsed allowed for code smuggling into the resulting cgo binary.

A discrepancy between how Go and C/C++ comments were parsed allowed for code smuggling into the resulting cgo binary.

A discrepancy between how Go and C/C++ comments were parsed allowed for code smuggling into the resulting cgo binary.

A discrepancy between how Go and C/C++ comments were parsed allowed for code smuggling into the resulting cgo binary.

• CVE-2025-61726: limit parsed URL query parameters to mitigate excessive memory consumption during form parsing
• CVE-2025-61732: prevent cgo code smuggling by removing user-controlled content from documentation strings in generated ASTs

• Update to Go 1.25.7
• CVE-2025-61726: fixed DoS due to memory exhaustion flaw in net/url parameter parsing
• CVE-2025-61732: fixed RCE via code smuggling flaw in cgo comment parsing
• CVE-2025-68121: fixed security bypass in TLS where session resumption could ignore revoked or expired client certificates.
• CVE-2025-61731: fixed arbitrary code execution vulnerability in the go command toolchain involving unsafe cgo configuration flags.
• CVE-2025-68119: fixed arbitrary code execution risk when the go tool processes malicious version strings from external source control.
• CVE-2025-61730: fixed minor information disclosure in TLS 1.3 during specific encrypted handshake message transitions.
• CVE-2025-61727: fixed certificate validation bypass where specific wildcard domain constraints were not properly enforced by the security library.

A discrepancy between how Go and C/C++ comments were parsed allowed for code smuggling into the resulting cgo binary.

net/http: memory exhaustion in Request.ParseForm. (CVE-2025-61726) archive/zip: denial of service when parsing arbitrary ZIP archives. (CVE-2025-61728) crypto/tls: handshake messages may be processed at the incorrect encryption level. (CVE-2025-61730) cmd/go: bypass of flag sanitization can lead to arbitrary code execution. (CVE-2025-61731) Potential code smuggling via doc comments in cmd/cgo. (CVE-2025-61732) cmd/go: unexpected code execution when invoking toolchain. (CVE-2025-68119) crypto/tls: Config.Clone copies automatically generated session ticket keys, session resumption does not account for the expiration of full certificate chain. (CVE-2025-68121)

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

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

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

This update for go1.25 fixes the following issues:

Update to version 1.25.7.

Security issues fixed:

• CVE-2025-61732: cmd/go: discrepancy between Go and C/C++ comment parsing allows for C code smuggling (bsc#1257692).
• 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 updates and bugfixes:

• version update to 1.25.7:

  • go#75844 cmd/compile: OOM killed on linux/arm64
  • go#77323 crypto/x509: single-label excluded DNS name constraints incorrectly match all wildcard SANs
  • go#77425 crypto/tls: CL 737700 broke session resumption on macOS

This update for go1.24 fixes the following issues:

Update to version 1.24.13.

Security issues fixed:

• CVE-2025-61732: cmd/go: discrepancy between Go and C/C++ comment parsing allows for C code smuggling (bsc#1257692).
• 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-68119: cmd/go: unexpected code execution when invoking toolchain (bsc1256820).

Other updates and bugfixes:

• version update to 1.24.13:

  • go#77323 crypto/x509: single-label excluded DNS name constraints incorrectly match all wildcard SANs
  • go#77424 crypto/tls: CL 737700 broke session resumption on macOS

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 go1.25-openssl fixes the following issues

• Update to version go1.25.12 (bsc#1244485).
• CVE-2025-61732: cmd/cgo: discrepancy between Go and C/C++ comment parsing allows for C code smuggling (bsc#1257692).
• 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-2026-25679: net/url: reject IPv6 literal not at start of host (bsc#1259264).
• CVE-2026-27139: os: FileInfo can escape from a Root (bsc#1259268).
• CVE-2026-27140: cmd/go: trust layer bypass when using cgo and SWIG (bsc#1261653).
• CVE-2026-27142: html/template: URLs in meta content attribute actions are not escaped (bsc#1259265).
• CVE-2026-27143: cmd/compile: possible memory corruption after bound check elimination (bsc#1261654).
• CVE-2026-27144: cmd/compile: no-op interface conversion bypasses overlap checking (bsc#1261655).
• CVE-2026-27145: crypto/x509: split candidate hostname only once (bsc#1267450).
• CVE-2026-32280: crypto/x509: unexpected work during chain building (bsc#1261656).
• CVE-2026-32281: crypto/x509: inefficient policy validation (bsc#1261657).
• CVE-2026-32282: os: Root.Chmod can follow symlinks out of the root on Linux (bsc#1261658).
• CVE-2026-32283: crypto/tls: multiple key update handshake messages can cause connection to deadlock (bsc#1261659).
• CVE-2026-32288: archive/tar: unbounded allocation when parsing old format GNU sparse map (bsc#1261660).
• CVE-2026-32289: html/template: JS template literal context incorrectly tracked (bsc#1261661).
• CVE-2026-33811: net: crash when handling long CNAME response (bsc#1264508).
• CVE-2026-33814: net/http: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1264506).
• CVE-2026-39817: cmd/go: "go tool pack" does not sanitize output paths (bsc#1264505).
• CVE-2026-39819: cmd/go: "go bug" follows symlinks in predictable temporary filenames (bsc#1264504).
• CVE-2026-39820: net/mail: quadratic string concatentation in consumeComment (bsc#1264503).
• CVE-2026-39822: os: Root escape via symlink plus trailing slash (bsc#1271014).
• CVE-2026-39823: html/template: bypass of meta content URL escaping causes XSS (bsc#1264509).
• CVE-2026-39825: net/http/httputil: ReverseProxy forwards queries with more than urlmaxqueryparams parameters (bsc#1264500).
• CVE-2026-39826: html/template: escaper bypass leads to XSS (bsc#1264507).
• CVE-2026-39836: net: panic in Dial and LookupPort when handling NUL byte on Windows (bsc#1264501).
• CVE-2026-42499: net/mail: quadratic string concatenation in consumePhrase (bsc#1264502).
• CVE-2026-42501: cmd/go: malicious module proxy can bypass checksum database (bsc#1264499).
• CVE-2026-42504: mime: quadratic complexity in WordDecoder.DecodeHeader (bsc#1267442).
• CVE-2026-42505: crypto/tls: omit PSK in ECH outer client hello (bsc#1271015).
• CVE-2026-42507: net/textproto: arbitrary input are included in errors without any escaping (bsc#1267444).

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-61732 in the golang-1.24 package for Root:Debian:13. Multiple fixed versions available.

This update for govulncheck-vulndb fixes the following issues:

• Update to version 0.0.20260205T172317 2026-02-05T17:23:17Z. Refs jsc#PED-11136 Go CVE Numbering Authority IDs added or updated with aliases:

  • GO-2026-4337 CVE-2025-68121
  • GO-2026-4357 CVE-2026-23954 GHSA-7f67-crqm-jgh7
  • GO-2026-4359 CVE-2026-23953 GHSA-x6jc-phwx-hp32
  • GO-2026-4395 CVE-2026-25499 GHSA-gwch-7m8v-7544
  • GO-2026-4396 CVE-2026-25059 GHSA-qmj2-8r24-xxcq
  • GO-2026-4397 CVE-2026-25060 GHSA-wf93-3ghh-h389
  • GO-2026-4398 GHSA-grh9-37g7-53mj
  • GO-2026-4403 CVE-2025-22873
  • GO-2026-4404 CVE-2025-70849 GHSA-mw8w-q3f7-2v85
  • GO-2026-4405 CVE-2026-25121 GHSA-5g94-c2wx-8pxw
  • GO-2026-4406 CVE-2026-25122 GHSA-6p9p-q6wh-9j89
  • GO-2026-4407 CVE-2026-24843 GHSA-qxx2-7h4c-83f4
  • GO-2026-4408 CVE-2026-24844 GHSA-vqqr-rmpc-hhg2
  • GO-2026-4409 CVE-2026-25145 GHSA-2w4f-9fgg-q2v9
  • GO-2026-4411 CVE-2026-25579 GHSA-hrr4-3wgr-68x3
  • GO-2026-4412 CVE-2026-25143 GHSA-rf4g-89h5-crcr
  • GO-2026-4413 CVE-2026-25578 GHSA-rh3r-8pxm-hg4w
  • GO-2026-4414 CVE-2026-25160 GHSA-8jmm-3xwx-w974
  • GO-2026-4415 CVE-2026-25161 GHSA-x4q4-7phh-42j9
  • GO-2026-4416 CVE-2026-25538 GHSA-8wpc-j9q9-j5m2
  • GO-2026-4417 CVE-2026-24514 GHSA-2pf9-vr92-6h3v
  • GO-2026-4418 CVE-2023-43631 GHSA-3mq9-xhgq-r7gj
  • GO-2026-4419 CVE-2026-24513 GHSA-4g2f-xcph-2335
  • GO-2026-4421 CVE-2026-24735 GHSA-5w5r-8xc6-2xhw
  • GO-2026-4422 CVE-2023-43632 GHSA-6jp5-grgh-jw42
  • GO-2026-4423 CVE-2026-1580 GHSA-9h3p-52vh-959w
  • GO-2026-4425 CVE-2025-62878 GHSA-jr3w-9vfr-c746
  • GO-2026-4426 CVE-2026-24512 GHSA-jx8c-56mg-h6vp
  • GO-2026-4428 CVE-2023-43633 GHSA-4c4v-42hc-72p6
  • GO-2026-4430 CVE-2023-43630 GHSA-phcg-h58r-gmcq
  • GO-2026-4432 CVE-2023-43634 GHSA-wc42-fcjp-v8vq
  • GO-2026-4433 CVE-2025-61732
  • GO-2026-4440 CVE-2025-47911
  • GO-2026-4441 CVE-2025-58190

• Update to version 0.0.20260204T190754 2026-02-04T19:07:54Z. Refs jsc#PED-11136 Go CVE Numbering Authority IDs added or updated with aliases:

  • GO-2026-4324 CVE-2026-23645 GHSA-pcjq-j3mq-jv5j
  • GO-2026-4327 CVE-2026-23742 GHSA-cc8m-98fm-rc9g
  • GO-2026-4329 CVE-2026-21696 GHSA-2497-gp99-2m74
  • GO-2026-4330 CVE-2026-22822 GHSA-77v3-r3jw-j2v2
  • GO-2026-4331 CVE-2025-69199 GHSA-8w7m-w749-rx98
  • GO-2026-4333 CVE-2026-23829 GHSA-54wq-72mp-cq7c
  • GO-2026-4334 CVE-2026-23517 GHSA-4r5r-ccr6-q6f6
  • GO-2026-4335 CVE-2026-23518 GHSA-63m5-974w-448v
  • GO-2026-4336 CVE-2026-22808 GHSA-gfpw-jgvr-cw4j
  • GO-2026-4343 CVE-2026-23847 GHSA-w836-5gpm-7r93
  • GO-2026-4344 CVE-2026-23849 GHSA-43mm-m3h2-3prc
  • GO-2026-4345 CVE-2026-23845 GHSA-6jxm-fv7w-rw5j
  • GO-2026-4346 CVE-2026-23851 GHSA-94c7-g2fj-7682
  • GO-2026-4347 CVE-2026-23850 GHSA-cv54-7wv7-qxcw
  • GO-2026-4348 CVE-2026-23991 GHSA-846p-jg2w-w324
  • GO-2026-4349 CVE-2026-23992 GHSA-fphv-w9fq-2525
  • GO-2026-4350 CVE-2026-23960 GHSA-cv78-6m8q-ph82
  • GO-2026-4351 CVE-2026-23990 GHSA-4xh5-jcj2-ch8q
  • GO-2026-4352 GHSA-r92c-9c7f-3pj8
  • GO-2026-4353 CVE-2026-24058 GHSA-pchf-49fh-w34r
  • GO-2026-4354 CVE-2026-23831 GHSA-273p-m2cw-6833
  • GO-2026-4355 CVE-2026-24117 GHSA-4c4x-jm2x-pf9j
  • GO-2026-4356 CVE-2026-24124 GHSA-j8hf-cp34-g4j7
  • GO-2026-4362 CVE-2026-20800 GHSA-2vgv-hgv4-22mh
  • GO-2026-4363 CVE-2026-20897 GHSA-393c-qgvj-3xph
  • GO-2026-4364 CVE-2026-20912 GHSA-4xx9-vc8v-87hv
  • GO-2026-4365 CVE-2026-0798 GHSA-8fwc-qjw5-rvgp
  • GO-2026-4366 CVE-2026-20888 GHSA-9cgq-wp42-4rpq
  • GO-2026-4367 CVE-2026-20736 GHSA-hgr3-x44x-33hx
  • GO-2026-4368 CVE-2026-20883 GHSA-j8xr-c56q-m8jj
  • GO-2026-4369 CVE-2026-20904 GHSA-qqgv-v353-cv8p
  • GO-2026-4370 CVE-2026-20750 GHSA-rw22-5hhq-pfpf
  • GO-2026-4377 CVE-2026-24686 GHSA-jqc5-w2xx-5vq4
  • GO-2026-4378 CVE-2026-24470 GHSA-mxxc-p822-2hx9
  • GO-2026-4379 CVE-2026-24738 GHSA-j49h-6577-5xwq
  • GO-2026-4380 CVE-2026-24740 GHSA-m855-r557-5rc5
  • GO-2026-4381 CVE-2026-22039 GHSA-8p9x-46gm-qfx2
  • GO-2026-4382 CVE-2026-23881 GHSA-r2rj-wwm5-x6mq
  • GO-2026-4384…