Summary
This update for google-guest-agent fixes the following issues:
- CVE-2026-78659: golang.org/x/net/http2: HTTP/2 server memory exhaustion due to Trailer headers (bsc#1286994).
- CVE-2026-78660: golang.org/x/net/http2: HTTP/2 transport accepts malformed framing-related headers (bsc#1287058).
- CVE-2026-78663: golang.org/x/net/http2: double flow control refund on HTTP/2 server streams (bsc#1287137).
- CVE-2026-78669: golang.org/x/net/http2: excessive CPU consumption from repeated initial window changes (bsc#1285283).
- CVE-2026-97032: golang.org/x/net/http2: HTTP/2 server crash due to HPACK encoder race (bsc#1287487).
Update to version 20261022.00:
- Update go dependencies (#641)
- Remove stale Go module version overrides in _service file
- Ship gce-workload-cert-refresh.timer (bsc#1273192)
- Wait for new account to become visible before adding to groups (#635)
- Update golang.org/x/crypto to v0.58.0
- Update golang.org/x/net to v0.61.0
- Validate username using unicode.IsSpace to reject all Unicode whitespace characters (#637)
- Update dependencies to latest (#636)
- fix octal digit comparison in morePermissive (#631)
- Remove KillMode from google-guest-agent-manager (#629)
- Fix SUSE Linux Micro 6+ (#628) (bsc#1253357)
- Exclude irrelevant tests on FreeBSD (#625)
- Replace abandoned serial dependency (#624)
- Add build rules for MWLID extension
Fixed packages 1
| Release | Package | Fixed in |
|---|---|---|
| SUSE · SLE Micro 6.0 Linux Micro 6.0 | google-guest-agent | 20261022.00-159998.1.1 |
Vulnerabilities 5
-
Critical 9.1
Double flow control refund on HTTP/2 server streams in net/http
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…
-
High 7.5
HTTP/2 server memory exhaustion due to Trailer headers in net/http
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 malicio…
-
High 7.5
HTTP/2 transport accepts malformed framing-related headers in net/http
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 header…
-
High 7.5
Excessive CPU consumption from repeated initial window changes in net/http
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.
-
High 7.5
HTTP/2 server crash due to HPACK encoder race in net/http
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 …
References
-
report
https://bugzilla.suse.com/1253357
-
report
https://bugzilla.suse.com/1273192
-
report
https://bugzilla.suse.com/1285283
-
report
https://bugzilla.suse.com/1286994
-
report
https://bugzilla.suse.com/1287058
-
report
https://bugzilla.suse.com/1287137
-
report
https://bugzilla.suse.com/1287487
-
web
https://www.suse.com/security/cve/CVE-2026-78659
-
web
https://www.suse.com/security/cve/CVE-2026-78660
-
web
https://www.suse.com/security/cve/CVE-2026-78663
-
web
https://www.suse.com/security/cve/CVE-2026-78669
-
web
https://www.suse.com/security/cve/CVE-2026-97032