CVE-2026-56866

When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connection to the idle pool. Because CONNECT requests do not have a request body, the server may interpret the trailing body bytes as a subsequent pipelined HTTP/1.1 request on the connection, leaving the pooled connection desynchronized and causing the next caller that reuses it to read the response to the injected request. In reverse proxies (including httputil.ReverseProxy) that forward CONNECT requests through a shared Transport, this can lead to cross-user response poisoning.

.

Security Fix(es):

On most platforms, Go uses the given system root certificates. However, in some narrower cases, the system trust stores may not be updated without further action. To defend against the narrower set of cases that may remain affected, a denylist was added in crypto/x509 to return an error when calling Verify with any of the known intermediate certificates that are no longer considered to be trustworthy.(CVE-2026-111943)

When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connection to the idle pool. Because CONNECT requests do not have a request body, the server may interpret the trailing body bytes as a subsequent pipelined HTTP/1.1 request on the connection, leaving the pooled connection desynchronized and causing the next caller that reuses it to read the response to the injected request. In reverse proxies (including httputil.ReverseProxy) that forward CONNECT requests through a shared Transport, this can lead to cross-user response poisoning.(CVE-2026-56866)

Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation to forward responses containing such headers to an HTTP/1 client when acting as a reverse proxy. If the HTTP/1 client also does not behave strictly enough, this can result in response smuggling.(CVE-2026-78660)

Parsing a multipart form can bypass memory limits and read an arbitrarily long line into memory when the remaining limit at the start of a part is less than 400 bytes.(CVE-2026-94440)

.

Security Fix(es):

On most platforms, Go uses the given system root certificates. However, in some narrower cases, the system trust stores may not be updated without further action. To defend against the narrower set of cases that may remain affected, a denylist was added in crypto/x509 to return an error when calling Verify with any of the known intermediate certificates that are no longer considered to be trustworthy.(CVE-2026-111943)

When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connection to the idle pool. Because CONNECT requests do not have a request body, the server may interpret the trailing body bytes as a subsequent pipelined HTTP/1.1 request on the connection, leaving the pooled connection desynchronized and causing the next caller that reuses it to read the response to the injected request. In reverse proxies (including httputil.ReverseProxy) that forward CONNECT requests through a shared Transport, this can lead to cross-user response poisoning.(CVE-2026-56866)

Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation to forward responses containing such headers to an HTTP/1 client when acting as a reverse proxy. If the HTTP/1 client also does not behave strictly enough, this can result in response smuggling.(CVE-2026-78660)

Parsing a multipart form can bypass memory limits and read an arbitrarily long line into memory when the remaining limit at the start of a part is less than 400 bytes.(CVE-2026-94440)

.

Security Fix(es):

When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connection to the idle pool. Because CONNECT requests do not have a request body, the server may interpret the trailing body bytes as a subsequent pipelined HTTP/1.1 request on the connection, leaving the pooled connection desynchronized and causing the next caller that reuses it to read the response to the injected request. In reverse proxies (including httputil.ReverseProxy) that forward CONNECT requests through a shared Transport, this can lead to cross-user response poisoning.(CVE-2026-56866)

Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation to forward responses containing such headers to an HTTP/1 client when acting as a reverse proxy. If the HTTP/1 client also does not behave strictly enough, this can result in response smuggling.(CVE-2026-78660)

Parsing a multipart form can bypass memory limits and read an arbitrarily long line into memory when the remaining limit at the start of a part is less than 400 bytes.(CVE-2026-94440)

.

Security Fix(es):

On most platforms, Go uses the given system root certificates. However, in some narrower cases, the system trust stores may not be updated without further action. To defend against the narrower set of cases that may remain affected, a denylist was added in crypto/x509 to return an error when calling Verify with any of the known intermediate certificates that are no longer considered to be trustworthy.(CVE-2026-111943)

When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connection to the idle pool. Because CONNECT requests do not have a request body, the server may interpret the trailing body bytes as a subsequent pipelined HTTP/1.1 request on the connection, leaving the pooled connection desynchronized and causing the next caller that reuses it to read the response to the injected request. In reverse proxies (including httputil.ReverseProxy) that forward CONNECT requests through a shared Transport, this can lead to cross-user response poisoning.(CVE-2026-56866)

Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation to forward responses containing such headers to an HTTP/1 client when acting as a reverse proxy. If the HTTP/1 client also does not behave strictly enough, this can result in response smuggling.(CVE-2026-78660)

Parsing a multipart form can bypass memory limits and read an arbitrarily long line into memory when the remaining limit at the start of a part is less than 400 bytes.(CVE-2026-94440)

When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connection to the idle pool. Because CONNECT requests do not have a request body, the server may interpret the trailing body bytes as a subsequent pipelined HTTP/1.1 request on the connection, leaving the pooled connection desynchronized and causing the next caller that reuses it to read the response to the injected request. In reverse proxies (including httputil.ReverseProxy) that forward CONNECT requests through a shared Transport, this can lead to cross-user response poisoning.

The golang packages provide the Go programming language compiler.

Security Fix(es):

• net/http: golang: golang: Denial of Service via crafted HTTP Range headers (CVE-2026-78667)
• crypto/tls: golang: crypto/tls: Denial of Service via multiple ECH outer extension references (CVE-2026-97031)
• net/http: net/http/internal/http2: golang.org/x/net/http2: net/http: Denial of Service via excessive HTTP/2 SETTINGS frames (CVE-2026-78669)
• golang: crypto/x509: Go: crypto/x509: mitigation for security concerns with a specific Certificate Authority (CVE-2026-111943)

Bug Fix(es) and Enhancement(s):

• Update Go to version 1.26.10+1 [almalinux-10.2.z] (JIRA:AlmaLinux-287191)

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

• net/http: golang: golang: Denial of Service via crafted HTTP Range headers (CVE-2026-78667)
• crypto/tls: golang: crypto/tls: Denial of Service via multiple ECH outer extension references (CVE-2026-97031)
• net/http: net/http/internal/http2: golang.org/x/net/http2: net/http: Denial of Service via excessive HTTP/2 SETTINGS frames (CVE-2026-78669)
• golang: crypto/x509: Go: crypto/x509: mitigation for security concerns with a specific Certificate Authority (CVE-2026-111943)

Bug Fix(es) and Enhancement(s):

• Update Go to version 1.26.10+1 [almalinux-9.8.z] (JIRA:AlmaLinux-287192)

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

• net/http: golang: golang: Denial of Service via crafted HTTP Range headers (CVE-2026-78667)
• crypto/tls: golang: crypto/tls: Denial of Service via multiple ECH outer extension references (CVE-2026-97031)
• net/http: net/http/internal/http2: golang.org/x/net/http2: net/http: Denial of Service via excessive HTTP/2 SETTINGS frames (CVE-2026-78669)
• golang: crypto/x509: Go: crypto/x509: mitigation for security concerns with a specific Certificate Authority (CVE-2026-111943)

Bug Fix(es) and Enhancement(s):

• Update Go to version 1.26.10+1 [almalinux-8.10.z] (JIRA:AlmaLinux-287193)

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.

When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connection to the idle pool. Because CONNECT requests do not have a request body, the server may interpret the trailing body bytes as a subsequent pipelined HTTP/1.1 request on the connection, leaving the pooled connection desynchronized and causing the next caller that reuses it to read the response to the injected request. In reverse proxies (including httputil.ReverseProxy) that forward CONNECT requests through a shared Transport, this can lead to cross-user response poisoning.

When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connection to the idle pool. Because CONNECT requests do not have a request body, the server may interpret the trailing body bytes as a subsequent pipelined HTTP/1.1 request on the connection, leaving the pooled connection desynchronized and causing the next caller that reuses it to read the response to the injected request. In reverse proxies (including httputil.ReverseProxy) that forward CONNECT requests through a shared Transport, this can lead to cross-user response poisoning.

When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connection to the idle pool. Because CONNECT requests do not have a request body, the server may interpret the trailing body bytes as a subsequent pipelined HTTP/1.1 request on the connection, leaving the pooled connection desynchronized and causing the next caller that reuses it to read the response to the injected request. In reverse proxies (including httputil.ReverseProxy) that forward CONNECT requests through a shared Transport, this can lead to cross-user response poisoning.

When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connection to the idle pool. Because CONNECT requests do not have a request body, the server may interpret the trailing body bytes as a subsequent pipelined HTTP/1.1 request on the connection, leaving the pooled connection desynchronized and causing the next caller that reuses it to read the response to the injected request. In reverse proxies (including httputil.ReverseProxy) that forward CONNECT requests through a shared Transport, this can lead to cross-user response poisoning.

When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connection to the idle pool. Because CONNECT requests do not have a request body, the server may interpret the trailing body bytes as a subsequent pipelined HTTP/1.1 request on the connection, leaving the pooled connection desynchronized and causing the next caller that reuses it to read the response to the injected request. In reverse proxies (including httputil.ReverseProxy) that forward CONNECT requests through a shared Transport, this can lead to cross-user response poisoning.

When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connection to the idle pool. Because CONNECT requests do not have a request body, the server may interpret the trailing body bytes as a subsequent pipelined HTTP/1.1 request on the connection, leaving the pooled connection desynchronized and causing the next caller that reuses it to read the response to the injected request. In reverse proxies (including httputil.ReverseProxy) that forward CONNECT requests through a shared Transport, this can lead to cross-user response poisoning.

When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connection to the idle pool. Because CONNECT requests do not have a request body, the server may interpret the trailing body bytes as a subsequent pipelined HTTP/1.1 request on the connection, leaving the pooled connection desynchronized and causing the next caller that reuses it to read the response to the injected request. In reverse proxies (including httputil.ReverseProxy) that forward CONNECT requests through a shared Transport, this can lead to cross-user response poisoning.

net/http: HTTP/2 server crash due to HPACK encoder race net/http: HTTP/2 server memory exhaustion due to Trailer headers crypto/tls: reject malformed ECH outer extension references cmd/go: checksum bypass for golang.org/fips140 cmd/go: checksum database bypass for golang.org/toolchain html/template: reset context tracking on consecutive template expressions html/template: recognize |yield| as regexp preceder keyword net/textproto, mime/multipart: memory limit bypass when parsing MIME headers net/http: HTTP/1 client connection desynchronization after CONNECT rejection net/http: HTTP/1 server connection desynchronization after 2xx CONNECT response net/http: excessive CPU consumption from repeated initial window changes net/http: HTTP/2 transport accepts malformed framing-related headers net/http: lack of limit on size of parsed Range headers net/http: double flow control refund on HTTP/2 server streams

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

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

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

This update for go1.27 fixes the following issues:

Update to go1.27.2 (bsc#1272545):

• CVE-2026-56857: os: Root.Mkdir(All) can follow junctions out of the root on Windows (bsc#1284766).
• CVE-2026-56866: net/http: HTTP/1 client connection desynchronization after CONNECT rejection (bsc#1284767).
• CVE-2026-78659: net/http: HTTP/2 server memory exhaustion due to Trailer headers (bsc#1284768).
• CVE-2026-78660: net/http: HTTP/2 transport accepts malformed framing-related headers (bsc#1284769).
• CVE-2026-78663: net/http: double flow control refund on HTTP/2 server streams (bsc#1284770).
• CVE-2026-78667: net/http: lack of limit on size of parsed Range headers (bsc#1284771).
• CVE-2026-78669: net/http: excessive CPU consumption from repeated initial window changes (bsc#1284772).
• CVE-2026-94439: net/http: HTTP/1 server connection desynchronization after 2xx CONNECT response (bsc#1284773).
• CVE-2026-94440: net/textproto, mime/multipart: memory limit bypass when parsing MIME headers (bsc#1284774).
• CVE-2026-94444: cmd/go: checksum bypass for golang.org/fips140 (bsc#1284775).
• CVE-2026-94447: cmd/go: checksum database bypass for golang.org/toolchain (bsc#1284776).
• CVE-2026-94448: html/template: reset context tracking on consecutive template expressions (bsc#1284777).
• CVE-2026-97030: html/template: recognize yield as regexp preceder keyword (bsc#1284778).
• CVE-2026-97031: crypto/tls: reject malformed ECH outer extension references (bsc#1284779).
• CVE-2026-97032: net/http: HTTP/2 server crash due to HPACK encoder race (bsc#1284780).

Changes:

• go1.27.2 (released 2026-10-08) includes security fixes to the go command, and the crypto/tls, html/template, net/http, net/textproto, and os packages, as well as bug fixes to the compiler, the linker, the runtime, the cover tool, the go fix command, vet, and the compress/flate, crypto/mlkem, encoding/json, encoding/json/v2, net/http, and os packages.

• go#81084 encoding/json: Unmarshal leaves +/-Inf in the destination on float overflow in Go 1.27
• go#81145 runtime: mutex profiling can deadlock Windows asynchronous preemption during GC
• go#81226 runtime: netpoll: eventfd ready for something unexpected
• go#81229 encoding/json: json.UnsupportedValueError returns an Invalid Value instead of a Float value
• go#81233 compress/flate: Writer with a preset dictionary emits the dictionary into the output stream
• go#81252 lib/fips140: fix ML-KEM CAST and re-seal v1.26.0
• go#81296 cmd/compile: internal compiler error: MoveLoop too small
• go#81306 cmd/compile: go1.27.0 unified export data loses method order, breaking objectpath, crashing staticcheck
• go#81324 plugin: loading multiple plugins corrupts stdlib types in Go 1.27
• go#81353 runtime: Go 1.27.0: SIGSEGV crash with generic function + pointer type parameter + embedded interface
• go#81362 encoding/json: Marshal now honors MarshalText for string-kind map keys
• go#81374 os,internal/poll: NewFile on an inherited overlapped stdout pipe hangs a sibling's WriteFile (Windows)
• go#81389 cmd/fix, x/tools/go/analysis/passes/modernize: errorsastype rewrites errors.As target interface that does not implement error
• go#81402 os: go 1.25.x regression on RemoveAll for oldest Windows 10 build 10240
• go#81411 net/http: concurrent response body Read and Close can deadlock with automatic draining in Go 1.27
• go#81437 runtime: intermittent SIGBUS (unaligned access) in netpoll on mips64le (Go 1.27)
• go#81469 runtime: ios/arm64 binaries executed outside an app bundle change working directory on startup
• go#81515 net/http: readLoop reads Response.ContentLength after Body.Close returns
• go#81516 net/http: Response.Body.Close returns the earlier Read error after a non-EOF Read failure
• go#81522 net/http: Response.Trailer race due to response body draining
• go#81580 testing: go test -v doubles ESC (0x1b) in t.Log output since Go 1.27, corrupting ANSI colors in some terminals
• go#81666 cmd/compile: Embedded interfaces…

This update for go1.26 fixes the following issues:

Update to go 1.26.9 (bsc#1255111):

• CVE-2026-56857: os: Root.Mkdir(All) can follow junctions out of the root on Windows (bsc#1284766).
• CVE-2026-56866: net/http: HTTP/1 client connection desynchronization after CONNECT rejection (bsc#1284767).
• CVE-2026-78659: net/http: HTTP/2 server memory exhaustion due to Trailer headers (bsc#1284768).
• CVE-2026-78660: net/http: HTTP/2 transport accepts malformed framing-related headers (bsc#1284769).
• CVE-2026-78667: net/http: lack of limit on size of parsed Range headers (bsc#1284771).
• CVE-2026-94439: net/http: HTTP/1 server connection desynchronization after 2xx CONNECT response (bsc#1284773).
• CVE-2026-94440: net/textproto, mime/multipart: memory limit bypass when parsing MIME headers (bsc#1284774).
• CVE-2026-94444: cmd/go: checksum bypass for golang.org/fips140 (bsc#1284775).
• CVE-2026-94447: cmd/go: checksum database bypass for golang.org/toolchain (bsc#1284776).
• CVE-2026-94448: html/template: reset context tracking on consecutive template expressions (bsc#1284777).
• CVE-2026-97030: html/template: recognize yield as regexp preceder keyword (bsc#1284778).
• CVE-2026-97031: crypto/tls: reject malformed ECH outer extension references (bsc#1284779).
• CVE-2026-97032: net/http: HTTP/2 server crash due to HPACK encoder race (bsc#1284780).

Changes:

• go1.26.9 (released 2026-10-08) includes security fixes to the go command, and the crypto/tls, html/template, net/http, net/textproto, and os packages, as well as bug fixes to the compiler, the linker, the runtime, vet, and the crypto/mlkem, net/http, and os packages.

• go#81144 runtime: mutex profiling can deadlock Windows asynchronous preemption during GC
• go#81225 runtime: netpoll: eventfd ready for something unexpected
• go#81251 lib/fips140: fix ML-KEM CAST and re-seal v1.26.0
• go#81295 cmd/compile: internal compiler error: MoveLoop too small
• go#81318 os,internal/poll: NewFile on an inherited overlapped stdout pipe hangs a sibling's WriteFile (Windows)
• go#81401 os: go 1.25.x regression on RemoveAll for oldest Windows 10 build 10240
• go#81436 runtime: intermittent SIGBUS (unaligned access) in netpoll on mips64le (Go 1.27)
• go#81668 cmd/compile: go1.27 miscompiles &slice[i].Field on an append-built slice; returned pointer aliases reused memory
• go#81689 cmd/compile: slice allocation reuses stack backing store incorrectly
• go#81860 cmd/go: vet reports no diagnostics for a package that an earlier run vetted as a dependency
• go#81889 cmd/link: plugin.Open fails on macOS 27: LC_DYLD_CHAINED_FIXUPS seg_count not updated after combining DWARF

This update for go1.27 fixes the following issues:

Update to go1.27.2 (bsc#1272545):

• CVE-2026-56857: os: Root.Mkdir(All) can follow junctions out of the root on Windows (bsc#1284766).
• CVE-2026-56866: net/http: HTTP/1 client connection desynchronization after CONNECT rejection (bsc#1284767).
• CVE-2026-78659: net/http: HTTP/2 server memory exhaustion due to Trailer headers (bsc#1284768).
• CVE-2026-78660: net/http: HTTP/2 transport accepts malformed framing-related headers (bsc#1284769).
• CVE-2026-78663: net/http: double flow control refund on HTTP/2 server streams (bsc#1284770).
• CVE-2026-78667: net/http: lack of limit on size of parsed Range headers (bsc#1284771).
• CVE-2026-78669: net/http: excessive CPU consumption from repeated initial window changes (bsc#1284772).
• CVE-2026-94439: net/http: HTTP/1 server connection desynchronization after 2xx CONNECT response (bsc#1284773).
• CVE-2026-94440: net/textproto, mime/multipart: memory limit bypass when parsing MIME headers (bsc#1284774).
• CVE-2026-94444: cmd/go: checksum bypass for golang.org/fips140 (bsc#1284775).
• CVE-2026-94447: cmd/go: checksum database bypass for golang.org/toolchain (bsc#1284776).
• CVE-2026-94448: html/template: reset context tracking on consecutive template expressions (bsc#1284777).
• CVE-2026-97030: html/template: recognize yield as regexp preceder keyword (bsc#1284778).
• CVE-2026-97031: crypto/tls: reject malformed ECH outer extension references (bsc#1284779).
• CVE-2026-97032: net/http: HTTP/2 server crash due to HPACK encoder race (bsc#1284780).

Changes:

• go1.27.2 (released 2026-10-08) includes security fixes to the go command, and the crypto/tls, html/template, net/http, net/textproto, and os packages, as well as bug fixes to the compiler, the linker, the runtime, the cover tool, the go fix command, vet, and the compress/flate, crypto/mlkem, encoding/json, encoding/json/v2, net/http, and os packages.

• go#81084 encoding/json: Unmarshal leaves +/-Inf in the destination on float overflow in Go 1.27
• go#81145 runtime: mutex profiling can deadlock Windows asynchronous preemption during GC
• go#81226 runtime: netpoll: eventfd ready for something unexpected
• go#81229 encoding/json: json.UnsupportedValueError returns an Invalid Value instead of a Float value
• go#81233 compress/flate: Writer with a preset dictionary emits the dictionary into the output stream
• go#81252 lib/fips140: fix ML-KEM CAST and re-seal v1.26.0
• go#81296 cmd/compile: internal compiler error: MoveLoop too small
• go#81306 cmd/compile: go1.27.0 unified export data loses method order, breaking objectpath, crashing staticcheck
• go#81324 plugin: loading multiple plugins corrupts stdlib types in Go 1.27
• go#81353 runtime: Go 1.27.0: SIGSEGV crash with generic function + pointer type parameter + embedded interface
• go#81362 encoding/json: Marshal now honors MarshalText for string-kind map keys
• go#81374 os,internal/poll: NewFile on an inherited overlapped stdout pipe hangs a sibling's WriteFile (Windows)
• go#81389 cmd/fix, x/tools/go/analysis/passes/modernize: errorsastype rewrites errors.As target interface that does not implement error
• go#81402 os: go 1.25.x regression on RemoveAll for oldest Windows 10 build 10240
• go#81411 net/http: concurrent response body Read and Close can deadlock with automatic draining in Go 1.27
• go#81437 runtime: intermittent SIGBUS (unaligned access) in netpoll on mips64le (Go 1.27)
• go#81469 runtime: ios/arm64 binaries executed outside an app bundle change working directory on startup
• go#81515 net/http: readLoop reads Response.ContentLength after Body.Close returns
• go#81516 net/http: Response.Body.Close returns the earlier Read error after a non-EOF Read failure
• go#81522 net/http: Response.Trailer race due to response body draining
• go#81580 testing: go test -v doubles ESC (0x1b) in t.Log output since Go 1.27, corrupting ANSI colors in some terminals
• go#81666 cmd/compile: Embedded interfaces…

This update for go1.26 fixes the following issues:

Update to go 1.26.9 (bsc#1255111):

• CVE-2026-56857: os: Root.Mkdir(All) can follow junctions out of the root on Windows (bsc#1284766).
• CVE-2026-56866: net/http: HTTP/1 client connection desynchronization after CONNECT rejection (bsc#1284767).
• CVE-2026-78659: net/http: HTTP/2 server memory exhaustion due to Trailer headers (bsc#1284768).
• CVE-2026-78660: net/http: HTTP/2 transport accepts malformed framing-related headers (bsc#1284769).
• CVE-2026-78667: net/http: lack of limit on size of parsed Range headers (bsc#1284771).
• CVE-2026-94439: net/http: HTTP/1 server connection desynchronization after 2xx CONNECT response (bsc#1284773).
• CVE-2026-94440: net/textproto, mime/multipart: memory limit bypass when parsing MIME headers (bsc#1284774).
• CVE-2026-94444: cmd/go: checksum bypass for golang.org/fips140 (bsc#1284775).
• CVE-2026-94447: cmd/go: checksum database bypass for golang.org/toolchain (bsc#1284776).
• CVE-2026-94448: html/template: reset context tracking on consecutive template expressions (bsc#1284777).
• CVE-2026-97030: html/template: recognize yield as regexp preceder keyword (bsc#1284778).
• CVE-2026-97031: crypto/tls: reject malformed ECH outer extension references (bsc#1284779).
• CVE-2026-97032: net/http: HTTP/2 server crash due to HPACK encoder race (bsc#1284780).

Changes:

• go1.26.9 (released 2026-10-08) includes security fixes to the go command, and the crypto/tls, html/template, net/http, net/textproto, and os packages, as well as bug fixes to the compiler, the linker, the runtime, vet, and the crypto/mlkem, net/http, and os packages.

• go#81144 runtime: mutex profiling can deadlock Windows asynchronous preemption during GC
• go#81225 runtime: netpoll: eventfd ready for something unexpected
• go#81251 lib/fips140: fix ML-KEM CAST and re-seal v1.26.0
• go#81295 cmd/compile: internal compiler error: MoveLoop too small
• go#81318 os,internal/poll: NewFile on an inherited overlapped stdout pipe hangs a sibling's WriteFile (Windows)
• go#81401 os: go 1.25.x regression on RemoveAll for oldest Windows 10 build 10240
• go#81436 runtime: intermittent SIGBUS (unaligned access) in netpoll on mips64le (Go 1.27)
• go#81668 cmd/compile: go1.27 miscompiles &slice[i].Field on an append-built slice; returned pointer aliases reused memory
• go#81689 cmd/compile: slice allocation reuses stack backing store incorrectly
• go#81860 cmd/go: vet reports no diagnostics for a package that an earlier run vetted as a dependency
• go#81889 cmd/link: plugin.Open fails on macOS 27: LC_DYLD_CHAINED_FIXUPS seg_count not updated after combining DWARF

This update for go1.27 fixes the following issues:

Update to go1.27.2 (bsc#1272545):

• CVE-2026-56857: os: Root.Mkdir(All) can follow junctions out of the root on Windows (bsc#1284766).
• CVE-2026-56866: net/http: HTTP/1 client connection desynchronization after CONNECT rejection (bsc#1284767).
• CVE-2026-78659: net/http: HTTP/2 server memory exhaustion due to Trailer headers (bsc#1284768).
• CVE-2026-78660: net/http: HTTP/2 transport accepts malformed framing-related headers (bsc#1284769).
• CVE-2026-78663: net/http: double flow control refund on HTTP/2 server streams (bsc#1284770).
• CVE-2026-78667: net/http: lack of limit on size of parsed Range headers (bsc#1284771).
• CVE-2026-78669: net/http: excessive CPU consumption from repeated initial window changes (bsc#1284772).
• CVE-2026-94439: net/http: HTTP/1 server connection desynchronization after 2xx CONNECT response (bsc#1284773).
• CVE-2026-94440: net/textproto, mime/multipart: memory limit bypass when parsing MIME headers (bsc#1284774).
• CVE-2026-94444: cmd/go: checksum bypass for golang.org/fips140 (bsc#1284775).
• CVE-2026-94447: cmd/go: checksum database bypass for golang.org/toolchain (bsc#1284776).
• CVE-2026-94448: html/template: reset context tracking on consecutive template expressions (bsc#1284777).
• CVE-2026-97030: html/template: recognize yield as regexp preceder keyword (bsc#1284778).
• CVE-2026-97031: crypto/tls: reject malformed ECH outer extension references (bsc#1284779).
• CVE-2026-97032: net/http: HTTP/2 server crash due to HPACK encoder race (bsc#1284780).

Changes:

• go1.27.2 (released 2026-10-08) includes security fixes to the go command, and the crypto/tls, html/template, net/http, net/textproto, and os packages, as well as bug fixes to the compiler, the linker, the runtime, the cover tool, the go fix command, vet, and the compress/flate, crypto/mlkem, encoding/json, encoding/json/v2, net/http, and os packages.

• go#81084 encoding/json: Unmarshal leaves +/-Inf in the destination on float overflow in Go 1.27
• go#81145 runtime: mutex profiling can deadlock Windows asynchronous preemption during GC
• go#81226 runtime: netpoll: eventfd ready for something unexpected
• go#81229 encoding/json: json.UnsupportedValueError returns an Invalid Value instead of a Float value
• go#81233 compress/flate: Writer with a preset dictionary emits the dictionary into the output stream
• go#81252 lib/fips140: fix ML-KEM CAST and re-seal v1.26.0
• go#81296 cmd/compile: internal compiler error: MoveLoop too small
• go#81306 cmd/compile: go1.27.0 unified export data loses method order, breaking objectpath, crashing staticcheck
• go#81324 plugin: loading multiple plugins corrupts stdlib types in Go 1.27
• go#81353 runtime: Go 1.27.0: SIGSEGV crash with generic function + pointer type parameter + embedded interface
• go#81362 encoding/json: Marshal now honors MarshalText for string-kind map keys
• go#81374 os,internal/poll: NewFile on an inherited overlapped stdout pipe hangs a sibling's WriteFile (Windows)
• go#81389 cmd/fix, x/tools/go/analysis/passes/modernize: errorsastype rewrites errors.As target interface that does not implement error
• go#81402 os: go 1.25.x regression on RemoveAll for oldest Windows 10 build 10240
• go#81411 net/http: concurrent response body Read and Close can deadlock with automatic draining in Go 1.27
• go#81437 runtime: intermittent SIGBUS (unaligned access) in netpoll on mips64le (Go 1.27)
• go#81469 runtime: ios/arm64 binaries executed outside an app bundle change working directory on startup
• go#81515 net/http: readLoop reads Response.ContentLength after Body.Close returns
• go#81516 net/http: Response.Body.Close returns the earlier Read error after a non-EOF Read failure
• go#81522 net/http: Response.Trailer race due to response body draining
• go#81580 testing: go test -v doubles ESC (0x1b) in t.Log output since Go 1.27, corrupting ANSI colors in some terminals
• go#81666 cmd/compile: Embedded interfaces…

This update for go1.26 fixes the following issues:

Update to go 1.26.9 (bsc#1255111):

• CVE-2026-56857: os: Root.Mkdir(All) can follow junctions out of the root on Windows (bsc#1284766).
• CVE-2026-56866: net/http: HTTP/1 client connection desynchronization after CONNECT rejection (bsc#1284767).
• CVE-2026-78659: net/http: HTTP/2 server memory exhaustion due to Trailer headers (bsc#1284768).
• CVE-2026-78660: net/http: HTTP/2 transport accepts malformed framing-related headers (bsc#1284769).
• CVE-2026-78667: net/http: lack of limit on size of parsed Range headers (bsc#1284771).
• CVE-2026-94439: net/http: HTTP/1 server connection desynchronization after 2xx CONNECT response (bsc#1284773).
• CVE-2026-94440: net/textproto, mime/multipart: memory limit bypass when parsing MIME headers (bsc#1284774).
• CVE-2026-94444: cmd/go: checksum bypass for golang.org/fips140 (bsc#1284775).
• CVE-2026-94447: cmd/go: checksum database bypass for golang.org/toolchain (bsc#1284776).
• CVE-2026-94448: html/template: reset context tracking on consecutive template expressions (bsc#1284777).
• CVE-2026-97030: html/template: recognize yield as regexp preceder keyword (bsc#1284778).
• CVE-2026-97031: crypto/tls: reject malformed ECH outer extension references (bsc#1284779).
• CVE-2026-97032: net/http: HTTP/2 server crash due to HPACK encoder race (bsc#1284780).

Changes:

• go1.26.9 (released 2026-10-08) includes security fixes to the go command, and the crypto/tls, html/template, net/http, net/textproto, and os packages, as well as bug fixes to the compiler, the linker, the runtime, vet, and the crypto/mlkem, net/http, and os packages.

• go#81144 runtime: mutex profiling can deadlock Windows asynchronous preemption during GC
• go#81225 runtime: netpoll: eventfd ready for something unexpected
• go#81251 lib/fips140: fix ML-KEM CAST and re-seal v1.26.0
• go#81295 cmd/compile: internal compiler error: MoveLoop too small
• go#81318 os,internal/poll: NewFile on an inherited overlapped stdout pipe hangs a sibling's WriteFile (Windows)
• go#81401 os: go 1.25.x regression on RemoveAll for oldest Windows 10 build 10240
• go#81436 runtime: intermittent SIGBUS (unaligned access) in netpoll on mips64le (Go 1.27)
• go#81668 cmd/compile: go1.27 miscompiles &slice[i].Field on an append-built slice; returned pointer aliases reused memory
• go#81689 cmd/compile: slice allocation reuses stack backing store incorrectly
• go#81860 cmd/go: vet reports no diagnostics for a package that an earlier run vetted as a dependency
• go#81889 cmd/link: plugin.Open fails on macOS 27: LC_DYLD_CHAINED_FIXUPS seg_count not updated after combining DWARF

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

Update to version 1.26.10 (bsc#1255111, jsc#SLE-18320):

• CVE-2026-56857: os: Root.Mkdir(All) can follow junctions out of the root on Windows (bsc#1284766).
• CVE-2026-56866: net/http: HTTP/1 client connection desynchronization after CONNECT rejection (bsc#1284767).
• CVE-2026-78659: net/http: HTTP/2 server memory exhaustion due to Trailer headers (bsc#1284768).
• CVE-2026-78660: net/http: HTTP/2 transport accepts malformed framing-related headers (bsc#1284769).
• CVE-2026-78663: net/http: double flow control refund on HTTP/2 server streams (bsc#1284770).
• CVE-2026-78667: net/http: lack of limit on size of parsed Range headers (bsc#1284771).
• CVE-2026-78669: net/http: excessive CPU consumption from repeated initial window changes (bsc#1284772).
• CVE-2026-94439: net/http: HTTP/1 server connection desynchronization after 2xx CONNECT response (bsc#1284773).
• CVE-2026-94440: net/textproto, mime/multipart: memory limit bypass when parsing MIME headers (bsc#1284774).
• CVE-2026-94444: cmd/go: checksum bypass for golang.org/fips140 (bsc#1284775).
• CVE-2026-94447: cmd/go: checksum database bypass for golang.org/toolchain (bsc#1284776).
• CVE-2026-94448: html/template: reset context tracking on consecutive template expressions (bsc#1284777).
• CVE-2026-97030: html/template: recognize yield as regexp preceder keyword (bsc#1284778).
• CVE-2026-97031: crypto/tls: reject malformed ECH outer extension references (bsc#1284779).
• CVE-2026-97032: net/http: HTTP/2 server crash due to HPACK encoder race (bsc#1284780).
• CVE-2026-111943: crypto/x509: mitigation for security concerns with a specific Certificate Authority (bsc#1286317, bsc#1286261).

Changes:

• go#81144 runtime: mutex profiling can deadlock Windows asynchronous preemption during GC
• go#81225 runtime: netpoll: eventfd ready for something unexpected
• go#81251 lib/fips140: fix ML-KEM CAST and re-seal v1.26.0
• go#81295 cmd/compile: internal compiler error: MoveLoop too small
• go#81318 os,internal/poll: NewFile on an inherited overlapped stdout pipe hangs a sibling's WriteFile (Windows)
• go#81401 os: go 1.25.x regression on RemoveAll for oldest Windows 10 build 10240
• go#81436 runtime: intermittent SIGBUS (unaligned access) in netpoll on mips64le (Go 1.27)
• go#81668 cmd/compile: go1.27 miscompiles &slice[i].Field on an append-built slice; returned pointer aliases reused memory
• go#81689 cmd/compile: slice allocation reuses stack backing store incorrectly
• go#81860 cmd/go: vet reports no diagnostics for a package that an earlier run vetted as a dependency
• go#81889 cmd/link: plugin.Open fails on macOS 27: LC_DYLD_CHAINED_FIXUPS seg_count not updated after combining DWARF
• go#81152 cmd/compile/internal/test: TestMergeLocalsIntegration failures
• go#81113 debug/elf: applyRelocationsPPC was broken by CL 705075
• go#80889 os: TestRootMultiMkdirAllShallow failures on openbsd
• go#80851 cmd/go: pseudo #cgo directive FFLAGS value mixed up with CXXFLAGS in Go 1.26
• go#80827 runtime: async preemption corrupts AVX (YMM) state on netbsd/amd64

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

Update to version 1.26.10 (bsc#1255111, jsc#SLE-18320):

• CVE-2026-56857: os: Root.Mkdir(All) can follow junctions out of the root on Windows (bsc#1284766).
• CVE-2026-56866: net/http: HTTP/1 client connection desynchronization after CONNECT rejection (bsc#1284767).
• CVE-2026-78659: net/http: HTTP/2 server memory exhaustion due to Trailer headers (bsc#1284768).
• CVE-2026-78660: net/http: HTTP/2 transport accepts malformed framing-related headers (bsc#1284769).
• CVE-2026-78663: net/http: double flow control refund on HTTP/2 server streams (bsc#1284770).
• CVE-2026-78667: net/http: lack of limit on size of parsed Range headers (bsc#1284771).
• CVE-2026-78669: net/http: excessive CPU consumption from repeated initial window changes (bsc#1284772).
• CVE-2026-94439: net/http: HTTP/1 server connection desynchronization after 2xx CONNECT response (bsc#1284773).
• CVE-2026-94440: net/textproto, mime/multipart: memory limit bypass when parsing MIME headers (bsc#1284774).
• CVE-2026-94444: cmd/go: checksum bypass for golang.org/fips140 (bsc#1284775).
• CVE-2026-94447: cmd/go: checksum database bypass for golang.org/toolchain (bsc#1284776).
• CVE-2026-94448: html/template: reset context tracking on consecutive template expressions (bsc#1284777).
• CVE-2026-97030: html/template: recognize yield as regexp preceder keyword (bsc#1284778).
• CVE-2026-97031: crypto/tls: reject malformed ECH outer extension references (bsc#1284779).
• CVE-2026-97032: net/http: HTTP/2 server crash due to HPACK encoder race (bsc#1284780).
• CVE-2026-111943: crypto/x509: mitigation for security concerns with a specific Certificate Authority (bsc#1286317, bsc#1286261).

Changes:

• go#81144 runtime: mutex profiling can deadlock Windows asynchronous preemption during GC
• go#81225 runtime: netpoll: eventfd ready for something unexpected
• go#81251 lib/fips140: fix ML-KEM CAST and re-seal v1.26.0
• go#81295 cmd/compile: internal compiler error: MoveLoop too small
• go#81318 os,internal/poll: NewFile on an inherited overlapped stdout pipe hangs a sibling's WriteFile (Windows)
• go#81401 os: go 1.25.x regression on RemoveAll for oldest Windows 10 build 10240
• go#81436 runtime: intermittent SIGBUS (unaligned access) in netpoll on mips64le (Go 1.27)
• go#81668 cmd/compile: go1.27 miscompiles &slice[i].Field on an append-built slice; returned pointer aliases reused memory
• go#81689 cmd/compile: slice allocation reuses stack backing store incorrectly
• go#81860 cmd/go: vet reports no diagnostics for a package that an earlier run vetted as a dependency
• go#81889 cmd/link: plugin.Open fails on macOS 27: LC_DYLD_CHAINED_FIXUPS seg_count not updated after combining DWARF
• go#81152 cmd/compile/internal/test: TestMergeLocalsIntegration failures
• go#81113 debug/elf: applyRelocationsPPC was broken by CL 705075
• go#80889 os: TestRootMultiMkdirAllShallow failures on openbsd
• go#80851 cmd/go: pseudo #cgo directive FFLAGS value mixed up with CXXFLAGS in Go 1.26
• go#80827 runtime: async preemption corrupts AVX (YMM) state on netbsd/amd64

It was discovered that Go did not enforce a maximum recursion depth when parsing deeply nested ASN.1 structures. An attacker could possibly use this issue to cause Go to crash, resulting in a denial of service. (CVE-2026-33818)

It was discovered that Go incorrectly reset the depth counter when decoding XML elements. An attacker could possibly use this issue to cause Go to crash via deeply nested XML input, resulting in a denial of service. (CVE-2026-56859)

It was discovered that Go incorrectly handled TLS KeyUpdate messages after the handshake was completed. A remote attacker could possibly use this issue to cause Go to use excessive resources, leading to a denial of service. (CVE-2026-56862)

It was discovered that Go did not correctly verify checksum database tiles against their parents. An attacker in control of a malicious module proxy could possibly use this issue to bypass checksum database verification and serve malicious module content. (CVE-2026-56865)

It was discovered that the Go HTTP client incorrectly returned connections to the idle pool after a rejected HTTP/1 CONNECT request with a request body. A remote attacker could possibly use this issue to perform HTTP response poisoning attacks against reverse proxies. (CVE-2026-56866)

It was discovered that the Go HTTP/2 server did not apply header limits to Trailer headers. A remote attacker could possibly use this issue to cause Go to use excessive resources, leading to a denial of service. (CVE-2026-78659)

It was discovered that the Go HTTP/2 implementation did not remove malformed framing-related headers when forwarding responses. A remote attacker could possibly use this issue to perform HTTP response smuggling attacks when Go was acting as a reverse proxy. (CVE-2026-78660)

It was discovered that the Go HTTP/2 server could refund connection-level flow control twice for the same data under certain circumstances. A remote attacker could possibly use this issue to bypass the configured connection-level flow control limit. (CVE-2026-78663)

It was discovered that Go did not limit the size of Range headers parsed when serving content over HTTP. A remote attacker could possibly use this issue to cause Go to use excessive resources, leading to a denial of service. (CVE-2026-78667)

It was discovered that the Go HTTP/2 implementation incorrectly handled SETTINGS frames that changed the initial window size. A remote attacker could possibly use this issue to cause Go to use excessive resources, leading to a denial of service. (CVE-2026-78669)

It was discovered that the Go HTTP server continued to serve requests on a connection after sending a successful response to an HTTP/1 CONNECT request. A remote attacker could possibly use this issue to perform HTTP request smuggling attacks. (CVE-2026-94439)

It was discovered that Go did not enforce memory limits on the first line of a part when parsing multipart forms. A remote attacker could possibly use this issue to cause Go to use excessive resources, leading to a denial of service. (CVE-2026-94440)