Summary
This update for go1.26 fixes the following issues:
Changes in go1.26:
go1.26.1 (released 2026-03-05) includes security fixes to the
crypto/x509, html/template, net/url, and os packages, as well as
bug fixes to the go command, the go fix command, the compiler,
and the os and reflect packages. ( boo#1255111)
CVE-2026-25679 CVE-2026-27142 CVE-2026-27137 CVE-2026-27138 CVE-2026-27139
* go#77970 go#77578 boo#1259264 security: fix CVE-2026-25679 net/url: reject IPv6 literal not at start of host
* go#77972 go#77954 boo#1259265 security: fix CVE-2026-27142 html/template: URLs in meta content attribute actions are not escaped
* go#77973 go#77952 boo#1259266 security: fix CVE-2026-27137 crypto/x509: incorrect enforcement of email constraints
* go#77974 go#77953 boo#1259267 security: fix CVE-2026-27138 crypto/x509: panic in name constraint checking for malformed certificates
* go#77834 go#77827 boo#1259268 security: fix CVE-2026-27139 os: FileInfo can escape from a Root
* go#77252 cmd/compile: miscompile of global array initialization
* go#77407 os: Go 1.25.x regression on RemoveAll for windows
* go#77474 cmd/go: CGO compilation fails after upgrading from Go 1.25.5 to 1.25.6 due to --define-variable flag in pkg-config
* go#77529 cmd/fix, x/tools/go/analysis/passes/modernize: stringscut: OOB panic in indexArgValid analyzing "buf.Bytes()" call
* go#77532 net/smtp: expiry date of localhostCert for testing is too short
* go#77536 cmd/compile: internal compiler error: 'main.func1': not lowered: v15, Load STRUCT PTR SSA
* go#77618 strings: HasSuffix doesn't work correctly for multibyte runes in go 1.26
* go#77623 cmd/compile: internal compiler error on : "tried to free an already free register" with generic function and type >= 192 bytes
* go#77624 cmd/fix, x/tools/go/analysis/passes/modernize: stringsbuilder breaks code when combining two strings.Builders
* go#77680 cmd/link: TestFlagW/-w_-linkmode=external fails on illumos
* go#77766 cmd/fix,x/tools/go/analysis/passes/modernize: rangeint uses target platform's type in the range expression, breaking other platforms
* go#77780 reflect: breaking change for reflect.Value.Interface behaviour
* go#77786 cmd/compile: rewriteFixedLoad does not properly sign extend AuxInt
* go#77803 cmd/fix,x/tools/go/analysis/passes/modernize: reflect.TypeOf(nil) transformed into reflect.TypeFor[untyped nil]()
* go#77804 cmd/fix,x/tools/go/analysis/passes/modernize: minmax breaks select statements
* go#77805 cmd/fix, x/tools/go/analysis/passes/modernize: waitgroup leads to a compilation error
* go#77807 cmd/fix,x/tools/go/analysis/passes/modernize: stringsbuilder ignores variables if they are used multiple times
* go#77849 cmd/fix,x/tools/go/analysis/passes/modernize: stringscut rewrite changes behavior
* go#77860 cmd/go: change go mod init default go directive back to 1.N
* go#77899 cmd/fix, x/tools/go/analysis/passes/modernize: bad rangeint rewriting
* go#77904 x/tools/go/analysis/passes/modernize: stringsbuilder breaks code when GenDecl is a block declaration
go1.26.0 (released 2026-02-10) is a major release of Go.
go1.26.x minor releases will be provided through February 2027.
https://github.com/golang/go/wiki/Go-Release-Cycle
go1.26 arrives six months after Go 1.25. 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. (boo#1255111)
* Language change: The built-in new function, which creates a new
variable, now allows its operand to be an expression,
specifying the initial value of the variable.
* Language change: The restriction that a generic type may not
refer to itself in its type parameter list has been lifted. It
is now possible to specify type constraints that refer to the
generic type being constrained.
* go command: The venerable go fix command has been completely
revamped and is now the home of Go’s modernizers. It provides a
dependable, push-button way to update Go code bases to the
latest idioms and core library APIs. The initial suite of
modernizers includes dozens of fixers to make use of modern
features of the Go language and library, as well a source-level
inliner that allows users to automate their own API migrations
using //go:fix inline directives. These fixers should not
change the behavior of your program, so if you encounter any
issues with a fix performed by go fix, please report it.
* go command: The rewritten go fix command builds atop the exact
same Go analysis framework as go vet. This means the same
analyzers that provide diagnostics in go vet can be used to
suggest and apply fixes in go fix. The go fix command’s
historical fixers, all of which were obsolete, have been
removed.
* go command: Two upcoming Go blog posts will go into more detail
on modernizers, the inliner, and how to get the most out of go
fix.
* go command: go mod init now defaults to a lower go version in
new go.mod files. Running go mod init using a toolchain of
version 1.N.X will create a go.mod file specifying the Go
version go 1.(N-1).0. Pre-release versions of 1.N will create
go.mod files specifying go 1.(N-2).0. For example, the Go 1.26
release candidates will create go.mod files with go 1.24.0, and
Go 1.26 and its minor releases will create go.mod files with go
1.25.0. This is intended to encourage the creation of modules
that are compatible with currently supported versions of
Go. For additional control over the go version in new modules,
go mod init can be followed up with go get go@version.
* go command: cmd/doc, and go tool doc have been deleted. go doc
can be used as a replacement for go tool doc: it takes the same
flags and arguments and has the same behavior.
* pprof: The pprof tool w
Fixed packages 1
| Release | Package | Fixed in |
|---|---|---|
| openSUSE · Leap 16.0 | go1.26 | 1.26.1-160000.1.1 |
Vulnerabilities 5
-
High 7.5
Incorrect parsing of IPv6 host literals in net/url
url.Parse insufficiently validated the host/authority component and accepted some invalid URLs.
-
High 7.5
Incorrect enforcement of email constraints in crypto/x509
When verifying a certificate chain which contains a certificate containing multiple email address constraints which share common local portions but different domain portions, these constraints will not be properly applied, and only the last constraint will be…
-
Medium 6.1
URLs in meta content attribute actions are not escaped in html/template
Actions which insert URLs into the content attribute of HTML meta tags are not escaped. This can allow XSS if the meta tag also has an http-equiv attribute with the value "refresh". A new GODEBUG setting has been added, htmlmetacontenturlescape, which can be …
-
Medium 5.9
Panic in name constraint checking for malformed certificates in crypto/x509
Certificate verification can panic when a certificate in the chain has an empty DNS name and another certificate in the chain has excluded name constraints. This can crash programs that are either directly verifying X.509 certificate chains, or those that use…
-
Low 2.5
FileInfo can escape from a Root in os
On Unix platforms, when listing the contents of a directory using File.ReadDir or File.Readdir the returned FileInfo could reference a file outside of the Root in which the File was opened. The impact of this escape is limited to reading metadata provided by …
References
-
report
https://bugzilla.suse.com/1255111
-
report
https://bugzilla.suse.com/1259264
-
report
https://bugzilla.suse.com/1259265
-
report
https://bugzilla.suse.com/1259266
-
report
https://bugzilla.suse.com/1259267
-
report
https://bugzilla.suse.com/1259268
-
web
https://www.suse.com/security/cve/CVE-2026-25679
-
web
https://www.suse.com/security/cve/CVE-2026-27137
-
web
https://www.suse.com/security/cve/CVE-2026-27138
-
web
https://www.suse.com/security/cve/CVE-2026-27139
-
web
https://www.suse.com/security/cve/CVE-2026-27142