Summary
This update for google-guest-agent fixes the following issues
Security issues:
- CVE-2026-39821: Update golang.org/x/net/idna dependency (bsc#1266603).
- CVE-2026-39827: Update golang.org/x/crypto dependency (bsc#1266171).
- CVE-2026-39828: Update golang.org/x/crypto dependency (bsc#1266171).
- CVE-2026-39829: Update golang.org/x/crypto dependency (bsc#1266171).
- CVE-2026-39830: Update golang.org/x/crypto dependency (bsc#1266171).
- CVE-2026-39831: Update golang.org/x/crypto dependency (bsc#1266171).
- CVE-2026-39832: Update golang.org/x/crypto dependency (bsc#1266171).
- CVE-2026-39833: Update golang.org/x/crypto dependency (bsc#1266171).
- CVE-2026-39834: Update golang.org/x/crypto dependency (bsc#1266171).
- CVE-2026-39835: Update golang.org/x/crypto dependency (bsc#1266171).
- CVE-2026-42508: Update golang.org/x/crypto dependency (bsc#1266171).
- CVE-2026-46595: Update golang.org/x/crypto dependency (bsc#1266171).
- CVE-2026-46597: Update golang.org/x/crypto dependency (bsc#1266171).
- CVE-2026-46598: Update golang.org/x/crypto dependency (bsc#1266171).
- CVE-2023-45288: golang.org/x/net/http2: close connections when receiving too many headers (bsc#1236533).
- CVE-2024-45337: golang.org/x/crypto/ssh: Misuse of ServerConfig.PublicKeyCallback may cause authorization bypass in
golang.org/x/crypto (bsc#1234563).
- CVE-2025-22869: golang.org/x/crypto/ssh: Denial of Service in the Key Exchange of golang.org/x/crypto/ssh
(bsc#1239334).
- CVE-2025-58181: golang.org/x/crypto/ssh: invalidated number of mechanisms can cause unbounded memory consumption
(bsc#1253889).
- CVE-2026-33186: google.golang.org/grpc: authorization bypass due to improper validation of the HTTP/2 :path pseudo-
header (bsc#1260264).
- CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE
(bsc#1265762).
- CVE-2026-34986: github.com/go-jose/go-jose/v4: crafted JWE input with a missing encrypted key can lead to a denial of
service (bsc#1262926).
Fixed packages 5
| Release | Package | Fixed in |
|---|---|---|
| SUSE · SLE Micro 5.5 Linux Enterprise Micro 5.5 | google-guest-agent | 20260529.00-150000.1.70.1 |
| SUSE · SLES 15 SP4 Linux Enterprise Module for Public Cloud 15 SP4 | google-guest-agent | 20260529.00-150000.1.70.1 |
| SUSE · SLES 15 SP5 Linux Enterprise Module for Public Cloud 15 SP5 | google-guest-agent | 20260529.00-150000.1.70.1 |
| SUSE · SLES 15 SP6 Linux Enterprise Module for Public Cloud 15 SP6 | google-guest-agent | 20260529.00-150000.1.70.1 |
| SUSE · SLES 15 SP7 Linux Enterprise Module for Public Cloud 15 SP7 | google-guest-agent | 20260529.00-150000.1.70.1 |
Vulnerabilities 22
-
Critical 10.0CVE-2026-46595 Public exploit
Invoking VerifiedPublicKeyCallback permissions skip enforcement in golang.org/x/crypto/ssh
Previously, CVE-2024-45337 fixed an authorization bypass for misused ssh server configurations; if any other type of callback is passed other than public key, then the source-address validation would be skipped.
-
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 …
-
Critical 9.1CVE-2024-45337 Public exploit
Misuse of connection.serverAuthenticate may cause authorization bypass in golang.org/x/crypto
Applications and libraries which misuse connection.serverAuthenticate (via callback field ServerConfig.PublicKeyCallback) may be susceptible to an authorization bypass. The documentation for ServerConfig.PublicKeyCallback says that "A call to this function do…
-
Critical 9.1CVE-2026-33186 Public exploit
gRPC-Go has an authorization bypass via missing leading slash in :path
gRPC-Go is the Go language implementation of gRPC. Versions prior to 1.79.3 have an authorization bypass resulting from improper input validation of the HTTP/2 `:path` pseudo-header. The gRPC-Go server was too lenient in its routing logic, accepting requests …
-
Critical 9.1
Invoking client can cause server deadlock on unexpected responses in golang.org/x/crypto/ssh
A malicious SSH peer could send unsolicited global request responses to fill an internal buffer, blocking the connection's read loop. The blocked goroutine could not be released by calling Close(), resulting in a resource leak per connection. Unsolicited glob…
-
Critical 9.1
Invoking bypass of FIDO/U2F security keys physical interaction in golang.org/x/crypto/ssh
The Verify() method for FIDO/U2F security key types (sk-ecdsa-sha2-nistp256@openssh.com, sk-ssh-ed25519@openssh.com) did not check the User Presence flag. Signatures generated without physical touch were accepted, allowing unattended use of a hardware securit…
-
Critical 9.1
Invoking agent constraints dropped when forwarding keys in golang.org/x/crypto/ssh/agent
When adding a key to a remote agent constraint extensions such as restrict-destination-v00@openssh.com were not serialized in the request. Destination restrictions were silently stripped when forwarding keys, allowing unrestricted use of the key on the remote…
-
Critical 9.1
Invoking key constraints not enforced in golang.org/x/crypto/ssh/agent
The in-memory keyring returned by NewKeyring() silently accepted keys with the ConfirmBeforeUse constraint but never enforced it. The key would sign without any confirmation prompt, with no indication to the caller that the constraint was not in effect. NewKe…
-
Critical 9.1
Invoking infinite loop on large channel writes in golang.org/x/crypto/ssh
When writing data larger than 4GB in a single Write call on an SSH channel, an integer overflow in the internal payload size calculation caused the write loop to spin indefinitely, sending empty packets without making progress. The size comparison now uses in…
-
Critical 9.1
Invoking auth bypass via unenforced @revoked status in golang.org/x/crypto/ssh/knownhosts
Previously, a revoked 'SignatureKey' belonging to a CA was not correctly checked for revocation. Now, both the 'key' and 'key.SignatureKey' are checked for @revoked.
-
High 7.5
HTTP/2 CONTINUATION flood in net/http
An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames. Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a reques…
-
High 7.5
Unexpected memory consumption during token parsing in golang.org/x/oauth2
An attacker can pass a malicious malformed token which causes unexpected memory to be consumed during parsing.
-
High 7.5
Potential denial of service in golang.org/x/crypto
SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.
-
High 7.5
Infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE in net/http/internal/http2 in golang.org/x/net
When processing HTTP/2 SETTINGS frames, transport will enter an infinite loop of writing CONTINUATION frames if it receives a SETTINGS_MAX_FRAME_SIZE with a value of 0.
-
High 7.5
Go JOSE affect by a panic in JWE decryption
Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go, including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT) standards. Prior to 4.1.4 and 3.0.5, decrypting a JS…
-
High 7.5
Invoking pathological RSA/DSA parameters may cause DoS in golang.org/x/crypto/ssh
The RSA and DSA public key parsers did not enforce size limits on key parameters. A crafted public key with an excessively large modulus or DSA parameter could cause several minutes of CPU consumption during signature verification. This could be triggered by …
-
High 7.5
Invoking byte arithmetic causes underflow and panic in golang.org/x/crypto/ssh
An incorrectly placed cast from bytes to int allowed for server-side panic in the AES-GCM packet decoder for well-crafted inputs.
-
Medium 6.5
Invoking memory leak when rejecting channels can lead to DoS in golang.org/x/crypto/ssh
An authenticated SSH client that repeatedly opened channels which were rejected by the server caused unbounded memory growth, eventually crashing the server process and affecting all connected users. Rejected channels are now properly removed from the connect…
-
Medium 6.3
Invoking bypass of certificate restrictions in golang.org/x/crypto/ssh
When an SSH server authentication callback returned PartialSuccessError with non-nil Permissions, those permissions were silently discarded, potentially dropping certificate restrictions such as force-command after a second factor succeeded. Returning non-nil…
-
Medium 5.3
Unbounded memory consumption in golang.org/x/crypto/ssh
SSH servers parsing GSSAPI authentication requests do not validate the number of mechanisms specified in the request, allowing an attacker to cause unbounded memory consumption.
-
Medium 5.3
Invoking server panic during CheckHostKey/Authenticate in golang.org/x/crypto/ssh
SSH servers which use CertChecker as a public key callback without setting IsUserAuthority or IsHostAuthority could be caused to panic by a client presenting a certificate. CertChecker now returns an error instead of panicking when these callbacks are nil.
-
Medium 5.3
Invoking pathological inputs can lead to client panic in golang.org/x/crypto/ssh/agent
For certain crafted inputs, a 'ed25519.PrivateKey' was created by casting malformed wire bytes, leading to a panic when used.
References
-
report
https://bugzilla.suse.com/1210938
-
report
https://bugzilla.suse.com/1234563
-
report
https://bugzilla.suse.com/1236533
-
report
https://bugzilla.suse.com/1239334
-
report
https://bugzilla.suse.com/1239944
-
report
https://bugzilla.suse.com/1243254
-
report
https://bugzilla.suse.com/1243505
-
report
https://bugzilla.suse.com/1245759
-
report
https://bugzilla.suse.com/1253889
-
report
https://bugzilla.suse.com/1257010
-
report
https://bugzilla.suse.com/1260264
-
report
https://bugzilla.suse.com/1262926
-
report
https://bugzilla.suse.com/1265762
-
report
https://bugzilla.suse.com/1266171
-
report
https://bugzilla.suse.com/1266603
-
web
https://www.suse.com/security/cve/CVE-2023-45288
-
web
https://www.suse.com/security/cve/CVE-2024-45337
-
web
https://www.suse.com/security/cve/CVE-2025-22868
-
web
https://www.suse.com/security/cve/CVE-2025-22869
-
web
https://www.suse.com/security/cve/CVE-2025-58181
-
web
https://www.suse.com/security/cve/CVE-2026-33186
-
web
https://www.suse.com/security/cve/CVE-2026-33814
-
web
https://www.suse.com/security/cve/CVE-2026-34986
-
web
https://www.suse.com/security/cve/CVE-2026-39821
-
web
https://www.suse.com/security/cve/CVE-2026-39827
-
web
https://www.suse.com/security/cve/CVE-2026-39828
-
web
https://www.suse.com/security/cve/CVE-2026-39829
-
web
https://www.suse.com/security/cve/CVE-2026-39830
-
web
https://www.suse.com/security/cve/CVE-2026-39831
-
web
https://www.suse.com/security/cve/CVE-2026-39832
-
web
https://www.suse.com/security/cve/CVE-2026-39833
-
web
https://www.suse.com/security/cve/CVE-2026-39834
-
web
https://www.suse.com/security/cve/CVE-2026-39835
-
web
https://www.suse.com/security/cve/CVE-2026-42508
-
web
https://www.suse.com/security/cve/CVE-2026-46595
-
web
https://www.suse.com/security/cve/CVE-2026-46597
-
web
https://www.suse.com/security/cve/CVE-2026-46598