Source: golang-1.27
Version: 1.27~rc2-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: carnil@debian.org, Debian Security Team <team@security.debian.org>
Control: clone -1 -2 -3
Control: reassign -2 src:golang-1.26 1.26.5-1
Control: retitle -2 golang-1.26: CVE-2026-33818 CVE-2026-56853 CVE-2026-56858 CVE-2026-56859 CVE-2026-56860 CVE-2026-56862 CVE-2026-56864 CVE-2026-56865
Control: reassign -3 src:golang-1.25 1.25.12-1
Control: retitle -3 golang-1.25: CVE-2026-33818 CVE-2026-56853 CVE-2026-56858 CVE-2026-56859 CVE-2026-56860 CVE-2026-56862 CVE-2026-56864 CVE-2026-56865

Hi,

The following vulnerabilities were published for go.

CVE-2026-33818[0]:
| Enforce a recursion limit in Unmarshal to prevent stack exhaustion
| when parsing deeply-nested, recursive structures.


CVE-2026-56853[1]:
| 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.


CVE-2026-56858[2]:
| Previously, pathological inputs could close an unescaped '/' early,
| allowing for attack-controlled data to inject arbitrary content,
| potentially leading to XSS.


CVE-2026-56859[3]:
| Previously, DecodeElement would reset the depth counter causing it
| to never fire; this could lead to stack exhaustion.


CVE-2026-56860[4]:
| 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 buffer
| using index-based backtracking for '..' segments, eliminating the
| quadratic time complexity and significantly reducing memory
| allocations.


CVE-2026-56862[5]:
| 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
| derivation operations indefinitely.


CVE-2026-56864[6]:
| 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 transparency log.
| In order to determine if you have been affected:   rm -r go.sum
| go.work.sum vendor/ && go mod tidy


CVE-2026-56865[7]:
| 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 serve
| malicious module content that cannot be detected by evaluating the
| transparency log. All tiles are now correctly verified against their
| parents. In order to determine if you have been affected:   rm -r
| go.sum go.work.sum vendor/ && go mod tidy


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2026-33818
https://www.cve.org/CVERecord?id=CVE-2026-33818
[1] https://security-tracker.debian.org/tracker/CVE-2026-56853
https://www.cve.org/CVERecord?id=CVE-2026-56853
[2] https://security-tracker.debian.org/tracker/CVE-2026-56858
https://www.cve.org/CVERecord?id=CVE-2026-56858
[3] https://security-tracker.debian.org/tracker/CVE-2026-56859
https://www.cve.org/CVERecord?id=CVE-2026-56859
[4] https://security-tracker.debian.org/tracker/CVE-2026-56860
https://www.cve.org/CVERecord?id=CVE-2026-56860
[5] https://security-tracker.debian.org/tracker/CVE-2026-56862
https://www.cve.org/CVERecord?id=CVE-2026-56862
[6] https://security-tracker.debian.org/tracker/CVE-2026-56864
https://www.cve.org/CVERecord?id=CVE-2026-56864
[7] https://security-tracker.debian.org/tracker/CVE-2026-56865
https://www.cve.org/CVERecord?id=CVE-2026-56865

Regards,
Salvatore

We believe that the bug you reported is fixed in the latest version of
golang-1.25, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1144342@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer <toddy@debian.org> (supplier of updated golang-1.25 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Sun, 16 Aug 2026 21:19:57 +0200
Source: golang-1.25
Architecture: source
Version: 1.25.13-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Compiler Team <team+go-compiler@tracker.debian.org>
Changed-By: Dr. Tobias Quathamer <toddy@debian.org>
Closes: 1144342
Changes:
 golang-1.25 (1.25.13-1) unstable; urgency=medium
 .
   * New upstream version 1.25.13 (Closes: #1144342)
     - CVE-2026-56865
       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 serve malicious module
       content that cannot be detected by evaluating the transparency log. All
       tiles are now correctly verified against their parents. In order to
       determine if you have been affected: rm -r go.sum go.work.sum vendor/ &&
       go mod tidy
     - CVE-2026-56864
       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 transparency log. In
       order to determine if you have been affected: rm -r go.sum go.work.sum
       vendor/ && go mod tidy
     - CVE-2026-56862
       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 derivation operations
       indefinitely.
     - CVE-2026-56860
       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 buffer using
       index-based backtracking for '..' segments, eliminating the quadratic
       time complexity and significantly reducing memory allocations.
     - CVE-2026-56859
       Previously, DecodeElement would reset the depth counter causing it to
       never fire; this could lead to stack exhaustion.
     - CVE-2026-56858
       Previously, pathological inputs could close an unescaped '/' early,
       allowing for attack-controlled data to inject arbitrary content,
       potentially leading to XSS.
     - CVE-2026-56853
       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.
     - CVE-2026-33818
       Enforce a recursion limit in Unmarshal to prevent stack exhaustion when
       parsing deeply-nested, recursive structures.
Checksums-Sha1:
 a9a86638a3bcef3fbceec57d8d417b25e94228e9 2925 golang-1.25_1.25.13-1.dsc
 68f855143bbb2d38aae5efb778b41181c59f40a1 32023100 golang-1.25_1.25.13.orig.tar.gz
 e4430796ac8e859ac3baefc68f54de09892a8096 833 golang-1.25_1.25.13.orig.tar.gz.asc
 85bee9377f5e1557bee0ad6142c9d1f5b5593c5e 48040 golang-1.25_1.25.13-1.debian.tar.xz
 fc146d08aabbb08bb936320622e0a47455ee7e98 6525 golang-1.25_1.25.13-1_amd64.buildinfo
Checksums-Sha256:
 293d2d32c719c6e5212368797c3538eef76da38b0a98f5bafb07f74656276c75 2925 golang-1.25_1.25.13-1.dsc
 1d7e2f70b1ee9b93c7df8efcca71f5adcc6a59797a4336c2d10171bd4c174614 32023100 golang-1.25_1.25.13.orig.tar.gz
 47c96af84fd4cd5dceb1502f57e0c2cf92b3a9b9f78b7478f109b040825f8721 833 golang-1.25_1.25.13.orig.tar.gz.asc
 3187bd9a41d3329d2c1b7da6769f23e5dcf7aae287651483fdd3d8a588656dd3 48040 golang-1.25_1.25.13-1.debian.tar.xz
 86d832896e1caabe1e8d391ade2932ab6511151139cf8b91352ef47c3544ec1b 6525 golang-1.25_1.25.13-1_amd64.buildinfo
Files:
 fa2ad3de8462b185dbe986ebfdef5396 2925 golang optional golang-1.25_1.25.13-1.dsc
 cc4e56c806b825017e39925bb6aeabd3 32023100 golang optional golang-1.25_1.25.13.orig.tar.gz
 59a8973788155700f50830ff8d35ea0b 833 golang optional golang-1.25_1.25.13.orig.tar.gz.asc
 d979513e8bd033feba940c60bd0e9337 48040 golang optional golang-1.25_1.25.13-1.debian.tar.xz
 e67c385eba158066ecfada640208ff56 6525 golang optional golang-1.25_1.25.13-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAmqCEdMACgkQEwLx8Dbr
6xn/Fw//ZFKZPh+ipYouvWyw1b877PVpV8RS+j9fJFKadVZxbvu2GqKfQyltrDas
RG0xVBKs6WejoHldWVBfC73BucsOtLLxLdPh5DC08828aJmwg6YH4WYMW8AHWN7N
bX/WAgu4xLJIhB8vFtOtAIoztH3L79CkH7rjCbrcXyy4r8Aa7/YnQ9LXh4kwKcQB
BgdAbJ1XBIHGbiYpN0+gZEnT1DJFfdwHSxmRh10QnWus4xp95xv3BNL86bIENnAB
EzgdzK7DnopBCPJVnpEPLnJVhvpJwUWj2hUn4fUZxMYbiYaGrpi6ffGJonJn6XbW
XwLb5GCrxINTDDvPIe1viu+xvz0VTw6oAKiN3SIey69KAMIH5BvNvP8TKLn4+8pI
+fv8M+3QLu2HLd9+7qZ9r+ocJXldLOXicrm/ckK0hIlOyvVA8G1ProjmVI4cxLNg
rw+e6ScVIVzTpPuvrGNyzmTTXgXBR+OMZEaAWR5iNFqW1txKeTi/PJbGc9twCuZ9
0sMSbAWzgh0vsqQZEpU6B4+0vxp9UsXWZxTUD9QGQ8lemamCjn7d/u+8ynRcKMls
sfd3EnSludiOjOOR5s/xogEJaABs6qHjjunZg0Dv1EIFFc/ibKp8zDmagL88yDF3
66vBbas4Ijv8jbEO55H7uoG9rMKoLvOiHvcwl+K2DNsBtkRl7S4=
=3zhb
-----END PGP SIGNATURE-----