Summary
This update for glab fixes the following issues:
Changes in glab:
- Update to version 1.114.0:
* feat(api): support dynamic custom headers for authenticating proxies
* feat(artifact-registry): add glab artifact-registry login --docker
* feat(artifact-registry): resolve artifact registries in the Docker
credential helper
* feat(mr): show source and target branches in view
* feat(update): detect more install methods for the upgrade nudge
* fix(cmdutils): resolve same-host SSH remotes to the right account
* fix(config): resolve YAML alias nodes in hosts config
* fix(git): detect "no git repository" by exit status, not message text
* fix: glab can not set group level variable masked or masked and hidden
- CVE-2026-39821: reject all-ASCII xn-- Punycode labels in the vendored
golang.org/x/net/idna package regardless of Go's unicode.Version (boo#1266614).
Fixed packages 1
| Release | Package | Fixed in |
|---|---|---|
| openSUSE · Leap 16.0 | glab | 1.114.0-bp160.1.1 |
Vulnerabilities 24
-
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.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
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
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
Incorrect Neutralization of Input During Web Page Generation in x/net in golang.org/x/net
The tokenizer incorrectly interprets tags with unquoted attribute values that end with a solidus character (/) as self-closing. When directly using Tokenizer, this can result in such tags incorrectly being marked as self-closing, and when using the Parse func…
-
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 6.1
Invoking incorrect handling of character references in DOCTYPE nodes in golang.org/x/net/html
Parsing arbitrary HTML which is then rendered using Render can result in an unexpected HTML tree. This can be leveraged to execute XSS attacks in applications that attempt to sanitize input HTML before rendering.
-
Medium 6.1
Invoking duplicate attributes can cause XSS in golang.org/x/net/html
Parsing arbitrary HTML which is then rendered using Render can result in an unexpected HTML tree. This can be leveraged to execute XSS attacks in applications that attempt to sanitize input HTML before rendering.
-
Medium 6.1
Invoking incorrect handling of HTML elements in foreign content in golang.org/x/net/html
Parsing arbitrary HTML which is then rendered using Render can result in an unexpected HTML tree. This can be leveraged to execute XSS attacks in applications that attempt to sanitize input HTML before rendering.
-
Medium 6.1
Invoking incorrect handling of namespaced elements in foreign content in golang.org/x/net/html
Parsing arbitrary HTML which is then rendered using Render can result in an unexpected HTML tree. This can be leveraged to execute XSS attacks in applications that attempt to sanitize input HTML before rendering.
-
Medium 6.0
go-retryablehttp can leak basic auth credentials to log files
go-retryablehttp prior to 0.7.7 did not sanitize urls when writing them to its log file. This could lead to go-retryablehttp writing sensitive HTTP basic auth credentials to its log file. This vulnerability, CVE-2024-6104, was fixed in go-retryablehttp 0.7.7.
-
Medium 5.3
Non-linear parsing of case-insensitive content in golang.org/x/net/html
An attacker can craft an input to the Parse functions that would be processed non-linearly with respect to its length, resulting in extremely slow parsing. This could cause a denial of service.
-
Medium 5.3
Quadratic parsing complexity in golang.org/x/net/html
The html.Parse function in golang.org/x/net/html has quadratic parsing complexity when processing certain inputs, which can lead to denial of service (DoS) if an attacker provides specially crafted HTML content.
-
Medium 5.3
Infinite parsing loop in golang.org/x/net
The html.Parse function in golang.org/x/net/html has an infinite parsing loop when processing certain inputs, which can lead to denial of service (DoS) if an attacker provides specially crafted HTML content.
-
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/1227037
-
report
https://bugzilla.suse.com/1235353
-
report
https://bugzilla.suse.com/1241815
-
report
https://bugzilla.suse.com/1251467
-
report
https://bugzilla.suse.com/1251685
-
report
https://bugzilla.suse.com/1265775
-
report
https://bugzilla.suse.com/1265832
-
report
https://bugzilla.suse.com/1266172
-
report
https://bugzilla.suse.com/1266614
-
report
https://bugzilla.suse.com/1267155
-
web
https://www.suse.com/security/cve/CVE-2024-45338
-
web
https://www.suse.com/security/cve/CVE-2024-6104
-
web
https://www.suse.com/security/cve/CVE-2025-22872
-
web
https://www.suse.com/security/cve/CVE-2025-47911
-
web
https://www.suse.com/security/cve/CVE-2025-58190
-
web
https://www.suse.com/security/cve/CVE-2026-25681
-
web
https://www.suse.com/security/cve/CVE-2026-27136
-
web
https://www.suse.com/security/cve/CVE-2026-33814
-
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-42502
-
web
https://www.suse.com/security/cve/CVE-2026-42506
-
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