Summary
This update for go1.25 fixes the following issues:
go1.25.3 (released 2025-10-13) includes fixes to the crypto/x509
package. (bsc#1244485 CVE-2025-58187)
* go#75861 crypto/x509: TLS validation fails for FQDNs with trailing dot
* go#75777 spec: Go1.25 spec should be dated closer to actual release date
* Further fixups to the fix for net/url allowing IP literals with IPv4 mapped IPv6 addresses.
Fixed packages 15
| Release | Package | Fixed in |
|---|---|---|
| SUSE · Enterprise Storage 7.1 | go1.25 | 1.25.3-150000.1.19.1 |
| openSUSE · Leap 15.6 | go1.25 | 1.25.3-150000.1.19.1 |
| SUSE · SLE HPC 15 SP3 Linux Enterprise High Performance Computing 15 SP3-LTSS | go1.25 | 1.25.3-150000.1.19.1 |
| SUSE · SLE HPC 15 SP4 Linux Enterprise High Performance Computing 15 SP4-ESPOS | go1.25 | 1.25.3-150000.1.19.1 |
| SUSE · SLE HPC 15 SP4 Linux Enterprise High Performance Computing 15 SP4-LTSS | go1.25 | 1.25.3-150000.1.19.1 |
| SUSE · SLE HPC 15 SP5 Linux Enterprise High Performance Computing 15 SP5-ESPOS | go1.25 | 1.25.3-150000.1.19.1 |
| SUSE · SLE HPC 15 SP5 Linux Enterprise High Performance Computing 15 SP5-LTSS | go1.25 | 1.25.3-150000.1.19.1 |
| SUSE · SLES 15 SP6 Linux Enterprise Module for Development Tools 15 SP6 | go1.25 | 1.25.3-150000.1.19.1 |
| SUSE · SLES 15 SP7 Linux Enterprise Module for Development Tools 15 SP7 | go1.25 | 1.25.3-150000.1.19.1 |
| SUSE · SLES 15 SP3 Linux Enterprise Server 15 SP3-LTSS | go1.25 | 1.25.3-150000.1.19.1 |
| SUSE · SLES 15 SP4 Linux Enterprise Server 15 SP4-LTSS | go1.25 | 1.25.3-150000.1.19.1 |
| SUSE · SLES 15 SP5 Linux Enterprise Server 15 SP5-LTSS | go1.25 | 1.25.3-150000.1.19.1 |
| SUSE · SLES for SAP 15 SP3 Linux Enterprise Server for SAP Applications 15 SP3 | go1.25 | 1.25.3-150000.1.19.1 |
| SUSE · SLES for SAP 15 SP4 Linux Enterprise Server for SAP Applications 15 SP4 | go1.25 | 1.25.3-150000.1.19.1 |
| SUSE · SLES for SAP 15 SP5 Linux Enterprise Server for SAP Applications 15 SP5 | go1.25 | 1.25.3-150000.1.19.1 |
Vulnerabilities 1
-
High 7.5
Quadratic complexity when checking name constraints in crypto/x509
Due to the design of the name constraint checking algorithm, the processing time of some inputs scale non-linearly with respect to the size of the certificate. This affects programs which validate arbitrary certificate chains.