Summary
This update for go1.27 fixes the following issues:
- go1.27.0 (released 2026-08-19) is a major release of Go.
go1.27.x minor releases will be provided through August 2027.
https://github.com/golang/go/wiki/Go-Release-Cycle
go1.27 arrives six months after Go 1.26. Most of its changes are
in the implementation of the toolchain, runtime, and
libraries. As always, the release maintains the Go 1 promise of
compatibility. We expect almost all Go programs to continue to
compile and run as before. (bsc#1272545)
* Language change: Go 1.27 now supports generic methods: a method
declaration may declare its own type parameters. This widely
anticipated change allows adding generic functions within the
namespace of a particular data type where before one had to
declare such functions with a scope of the entire package.
* Language change: A key in a struct literal may now be any valid
field selector for the struct type, not just a (top-level)
field name of the struct.
* Language change: Function type inference has been generalized
to apply in all contexts where a generic function is assigned
to a variable of (or converted to) a matching function type.
* Tools: Response file (@file) parsing is now supported for the
compile, link, asm, cgo, cover, and pack tools. The response
file contains whitespace-separated arguments with support for
single-quoted and double-quoted strings, escape sequences, and
backslash-newline line continuation. The format is compatible
with GCC’s response file implementation to ensure
interoperability with existing build systems.
* go command: The go command no longer has support for the bzr
version control system. It will no longer be able to directly
fetch modules hosted on bzr servers.
* godebug: Starting with Go 1.27, the go command now recognizes a
GODEBUG setting for which support was removed (such as
asynctimerchan, see below) if it appears in go.mod files
(godebug entries) and .go source files (//go:debug
comments). It accepts these settings if they are set to the
final default value established before the setting was
removed. If they are set to an old value, the go command will
fail. This change is in the spirit of the Go 1 compatibility
guarantee and allows existing programs that set supported
GODEBUG settings to continue to build and run without changes
even when the respective setting support has been removed.
* go test: go test now invokes the stdversion vet check by
default. This reports the use of standard library symbols that
are too new for the Go version in force in the referring file,
as determined by go directive in go.mod and build tags on the
file.
* go test: go test -json now annotates 'Action':'output' lines
with an optional new field 'OutputType', specifying the type of
output. Currently, the possible values include “error”,
“error-continue”, and “frame”. See cmd/test2json help for
details.
* go doc: The go doc command now supports package@version syntax,
such as go doc example.com/pkg@v1.2.3.
* go doc: The go doc command now accepts the -ex command-line
option to list executable examples of the given package or
symbol. When an example name is passed on the command line
(such as go doc bytes.ExampleBuffer), go doc now prints the
example source code along with comments.
* go fix: The go fix command contains several new modernizers
(atomictypes, embedlit, slicesbackward, and unsafefuncs).
* go fix: The existing fmtappendf analyzer was removed due to
stylistic concerns.
* go fix: The existing waitgroup analyzer was renamed to
waitgroupgo to avoid ambiguity.
* go mod tidy: For modules specifying go 1.27 or later in their
go.mod file, go mod tidy now automatically merges duplicate
require blocks. This ensures the file maintains a clean,
standard structure containing at most two require blocks: one
for direct dependencies and one for indirect dependencies.
* go mod fix: Existing comment blocks attached to dependencies
are preserved during this consolidation. If a comment block is
associated with a mixed set of directives (containing both
direct and indirect dependencies), the comment block is merged
and attached to the new direct dependency block.
* go mod fix: Previously, if a go.mod file accumulated multiple
disjoint require blocks (often due to manual edits, unresolved
Git merge conflicts, or legacy upgrades) go mod tidy would
leave the extra blocks intact or inadvertently create new
ones. The tool now strictly enforces the two-block layout,
consolidating disparate requirements into their respective
blocks and cleaning up the structure of the module file
automatically.
* go tool trace: go tool trace’s -http command-line option now
restricts the listen address to localhost when passed only a
port (e.g., -http=:6060). This change makes go tool trace
consistent with the behavior of go tool pprof’s -http flag. To
listen on all addresses, explicitly include the specified
address (e.g., -http=0.0.0.0:6060).
* runtime: Tracebacks for modules with go directives configuring
Go 1.27 or later will now include runtime/pprof goroutine
labels in the header line. This behavior can be disabled with
tracebacklabels=0 GODEBUG setting (added in Go 1.26). This
opt-out is expected to be kept indefinitely in case goroutine
labels acquire sensitive information that shouldn’t be made
available in tracebacks.
* runtime: The asynctimerchan GODEBUG setting (added in Go 1.23)
has been removed permanently. Channels created by package time
are now always unbuffered (synchronous), irrespective of
GODEBUG settings.
* runtime: Faster memory allocation. The compiler now generates
calls to size-specialized memory allocation routines, reducing
the cost
Fixed packages 11
| Release | Package | Fixed in |
|---|---|---|
| SUSE · SLE HPC 15 SP4 Linux Enterprise High Performance Computing 15 SP4-ESPOS | go1.27 | 1.27.0-150000.1.6.1 |
| SUSE · SLE HPC 15 SP4 Linux Enterprise High Performance Computing 15 SP4-LTSS | go1.27 | 1.27.0-150000.1.6.1 |
| SUSE · SLE HPC 15 SP5 Linux Enterprise High Performance Computing 15 SP5-ESPOS | go1.27 | 1.27.0-150000.1.6.1 |
| SUSE · SLE HPC 15 SP5 Linux Enterprise High Performance Computing 15 SP5-LTSS | go1.27 | 1.27.0-150000.1.6.1 |
| SUSE · SLES 15 SP7 Linux Enterprise Module for Development Tools 15 SP7 | go1.27 | 1.27.0-150000.1.6.1 |
| SUSE · SLES 15 SP4 Linux Enterprise Server 15 SP4-LTSS | go1.27 | 1.27.0-150000.1.6.1 |
| SUSE · SLES 15 SP5 Linux Enterprise Server 15 SP5-LTSS | go1.27 | 1.27.0-150000.1.6.1 |
| SUSE · SLES 15 SP6 Linux Enterprise Server 15 SP6-LTSS | go1.27 | 1.27.0-150000.1.6.1 |
| SUSE · SLES for SAP 15 SP4 Linux Enterprise Server for SAP Applications 15 SP4 | go1.27 | 1.27.0-150000.1.6.1 |
| SUSE · SLES for SAP 15 SP5 Linux Enterprise Server for SAP Applications 15 SP5 | go1.27 | 1.27.0-150000.1.6.1 |
| SUSE · SLES for SAP 15 SP6 Linux Enterprise Server for SAP Applications 15 SP6 | go1.27 | 1.27.0-150000.1.6.1 |
Vulnerabilities 9
-
Critical 9.6
Invoking failure to reject ASCII-only Punycode-encoded labels in golang.org/x/net/idna
The ToASCII and ToUnicode functions incorrectly accept Punycode-encoded labels that decode to an ASCII-only label. For example, ToUnicode("xn--example-.com") incorrectly returns the name "example.com" rather than an error. This behavior can lead to privilege …
-
High 8.4
Fix transparency log tile verification bypass in golang.org/x/mod/sumdb/tlog
A malicious GOPROXY was previously capable of forging up to two sumdb tiles that allow for a requested module to bypass the GOSUMDB check and persist attacker-controlled module content to a local Go module cache. This attack allows for a malicious GOPROXY to …
-
High 7.5
Enforce maximum recursion depth in encoding/asn1
Enforce a recursion limit in Unmarshal to prevent stack exhaustion when parsing deeply-nested, recursive structures.
-
High 7.5
Apply ReadHeaderTimeout when doing unencrypted HTTP/2 check in net/http
When a server is configured to support unencrypted HTTP/2, it reads a few bytes from each new connection to see if they contain the HTTP/2 client preface. ReadHeaderTimeout is unexpectedly not being applied when doing this.
-
High 7.5
Add recursion depth guard during decode in encoding/xml
Previously, DecodeElement would reset the depth counter causing it to never fire; this could lead to stack exhaustion.
-
High 7.5
Limit handshake messages we are willing to accept post-handshake in crypto/tls
Handshake messages, such as KeyUpdate, are always considered as state-advancing, regardless of whether a handshake has been completed or not. As a result, a malicious client can keep sending KeyUpdate messages to force the server to keep performing key deriva…
-
High 7.5
Ignore unrelated, unauthenticated hashes in Lookup in golang.org/x/mod/sumdb
A malicious GOSUMDB was capable of serving arbitrary module content not contained within the transparency log. This attack allows for a coordinating GOPROXY and GOSUMDB to serve a client malicious module content that cannot be detected by evaluating the trans…
-
Medium 6.1
Fix Javascript regexp context tracking in html/template
Previously, pathological inputs could close an unescaped '/' early, allowing for attack-controlled data to inject arbitrary content, potentially leading to XSS.
-
Medium 5.9
Avoid quadratic complexity in resolvePath in net/url
Previously, resolving relative paths containing parent directory ('..') segments performed string conversions and buffer rewrites on each step, resulting in quadratic time complexity and high memory allocation overhead. Now, path resolution operates on a byte…
References
-
report
https://bugzilla.suse.com/1266609
-
report
https://bugzilla.suse.com/1272545
-
report
https://bugzilla.suse.com/1275024
-
report
https://bugzilla.suse.com/1275025
-
report
https://bugzilla.suse.com/1275026
-
report
https://bugzilla.suse.com/1275028
-
report
https://bugzilla.suse.com/1275029
-
report
https://bugzilla.suse.com/1275032
-
report
https://bugzilla.suse.com/1275033
-
report
https://bugzilla.suse.com/1275034
-
web
https://www.suse.com/security/cve/CVE-2026-33818
-
web
https://www.suse.com/security/cve/CVE-2026-39821
-
web
https://www.suse.com/security/cve/CVE-2026-56853
-
web
https://www.suse.com/security/cve/CVE-2026-56858
-
web
https://www.suse.com/security/cve/CVE-2026-56859
-
web
https://www.suse.com/security/cve/CVE-2026-56860
-
web
https://www.suse.com/security/cve/CVE-2026-56862
-
web
https://www.suse.com/security/cve/CVE-2026-56864
-
web
https://www.suse.com/security/cve/CVE-2026-56865