Описание
Security update for go1.27
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 using tail calls cause race detector stack growth
- go#81667 cmd/compile: go1.27 miscompiles &slice[i].Field on an append-built slice; returned pointer aliases reused memory
- go#81706 cmd/compile: ICE on 386 when inlining nested bit rotations (Int64Lo not lowered)
- go#81816 net/http: Request.TLS is not properly populated for HTTP/2 requests
- go#81818 cmd/internal/obj/ppc64: async preemption bug in BR (CTR)
- go#81829 runtime: windows/amd64 stack corruption when LockOSThread wraps registry calls (new in Go 1.27)
- go#81832 cmd/cover: NumStmt duplicated across split blocks, inflating statement coverage
- go#81861 cmd/go: vet reports no diagnostics for a package that an earlier run vetted as a dependency
- go#81890 cmd/link: plugin.Open fails on macOS 27: LC_DYLD_CHAINED_FIXUPS seg_count not updated after combining DWARF
Список пакетов
Container bci/golang:latest
SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS
SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS
SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
SUSE Linux Enterprise Module for Development Tools 15 SP7
SUSE Linux Enterprise Server 15 SP4-LTSS
SUSE Linux Enterprise Server 15 SP5-LTSS
SUSE Linux Enterprise Server 15 SP6-LTSS
SUSE Linux Enterprise Server for SAP Applications 15 SP4
SUSE Linux Enterprise Server for SAP Applications 15 SP5
SUSE Linux Enterprise Server for SAP Applications 15 SP6
Ссылки
- Link for SUSE-SU-2026:4625-1
- E-Mail link for SUSE-SU-2026:4625-1
- SUSE Security Ratings
- SUSE Bug 1272545
- SUSE Bug 1284766
- SUSE Bug 1284767
- SUSE Bug 1284768
- SUSE Bug 1284769
- SUSE Bug 1284770
- SUSE Bug 1284771
- SUSE Bug 1284772
- SUSE Bug 1284773
- SUSE Bug 1284774
- SUSE Bug 1284775
- SUSE Bug 1284776
- SUSE Bug 1284777
- SUSE Bug 1284778
- SUSE Bug 1284779
- SUSE Bug 1284780
- SUSE CVE CVE-2026-56857 page
Описание
On Windows, when the target of Root.Mkdir or Root.MkdirAll is a junction pointing to an empty location, the operation can create a directory at the junction target even when that target is located outside the root. This only applies to operations where the last path component is a junction (path/to/junction, but not path/junction/target).
Затронутые продукты
Ссылки
- CVE-2026-56857
- SUSE Bug 1284766
Описание
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
- SUSE Bug 1284767
Описание
When "Trailer" headers are sent by a client, the HTTP server internally uses the header values to populate the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs memory overhead. For HTTP/2 servers, a malicious client can exploit this by sending a "Trailer" header that declares a large number of fields, causing the server to allocate a disproportionate amount of memory while bypassing Server.MaxHeaderValueCount and Server.MaxHeaderBytes limits. This exploit is not applicable for HTTP/1 servers, which do not support multiplexing a large number of requests over one TCP connection, and whose Server.MaxHeaderBytes are calculated differently.
Затронутые продукты
Ссылки
- CVE-2026-78659
- SUSE Bug 1284768
Описание
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
- SUSE Bug 1284769
Описание
The HTTP/2 server can refund connection-level flow control twice for the same data: Once when a client resets a stream (refunding data for any sent-but-unread portion of the stream), and again when a request handler reads the buffered data. A malicious client can exploit this to bypass the configured connection-level flow control limit (MaxReceiveBufferPerConnection). Total buffered data is still limited by the concurrent stream limit and stream-level flow control.
Затронутые продукты
Ссылки
- CVE-2026-78663
- SUSE Bug 1284770
Описание
When parsing a Range header containing a large number of small ranges, FileServer(FS), ServeContent, and ServeFile(FS) can consume an excessive amount of CPU.
Затронутые продукты
Ссылки
- CVE-2026-78667
- SUSE Bug 1284771
Описание
A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGS_INITIAL_WINDOW_SIZE values.
Затронутые продукты
Ссылки
- CVE-2026-78669
- SUSE Bug 1284772
Описание
When an HTTP server handler sends a 2xx response to an HTTP/1 CONNECT request and returns without hijacking the connection, the server improperly continues to read and serve requests from the connection. Since a 2xx response to an HTTP/1 CONNECT converts the connection into a tunnel, the server should not treat the connection as continuing to contain HTTP. The impact of this misbehavior is mostly limited to potential request smuggling, where an intermediate proxy considers the data on the connection to be tunneled and the server considers it to be HTTP.
Затронутые продукты
Ссылки
- CVE-2026-94439
- SUSE Bug 1284773
Описание
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
- SUSE Bug 1284774
Описание
Previously, a user operating inside of a malicious Go project that defines a bogus golang.org/fips140 and operates a malicious GOMODPROXY the user chooses to connect to can serve an arbitrary module in its place. We now unpack the trusted ziphash for the bundled golang.org/fips140 module and construct its entry in the GOMODCACHE such that it can be verified by the toolchain.
Затронутые продукты
Ссылки
- CVE-2026-94444
- SUSE Bug 1284775
Описание
Previously, a user operating inside of a malicious Go project that defines a bogus golang.org/toolchain go.sum entry and operates a malicious GOMODPROXY the user chooses to use can bypass the intended checksum. We now ensure that golang.org/toolchain always goes to the network for the canonical checksum.
Затронутые продукты
Ссылки
- CVE-2026-94447
- SUSE Bug 1284776
Описание
When a JavaScript template literal contains consecutive expressions, the context tracking state was not properly reset upon entering a new expression. We now ensure that template-literal expression entries correctly reset context variables so all subsequent regular expression literals are accurately recognized and escaped.
Затронутые продукты
Ссылки
- CVE-2026-94448
- SUSE Bug 1284777
Описание
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.
Затронутые продукты
Ссылки
- CVE-2026-97030
- SUSE Bug 1284778
Описание
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result.
Затронутые продукты
Ссылки
- CVE-2026-97031
- SUSE Bug 1284779
Описание
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.
Затронутые продукты
Ссылки
- CVE-2026-97032
- SUSE Bug 1284780