CVE-2026-110924: Openssh: openssh: gssapi delegated credentials can be stored after a failed authentication

Published Oct 15, 2026
·
Updated

A flaw was found in OpenSSH sshd when GSSAPIAuthentication is enabled. A partial GSSAPI exchange left gssapiclient, including an exported name and credential, for a later authentication attempt on the same connection. sshgssapistorecreds stored delegated credentials even when sshgssapiuserok had not succeeded. The RHEL maintainer confirmed that this does not authorize a later login. The impact is storage of a delegated credential that userok did not accept. RHEL ships GSSAPIAuthentication yes. On RHEL 10, GSSAPIDelegateCredentials defaults to yes, and storecreds returns early only when that switch is off. This is not CVE-2026-60000 (MaxAuthTries and GSSAPI) and not CVE-2026-3497 (GSSAPI key exchange).

Other sources

CVE-2026-110924 has been marked as a duplicate of CVE-2026-106553.

— Launchpad

Openssh: openssh: gssapi delegated credentials can be stored after a failed authentication

— Microsoft

Affected Software

7 affected components
OpenSSH OpenSSH
ubuntu/openssh-ssh1*
ubuntu/openssh-ssh1*
ubuntu/openssh-ssh1*
ubuntu/openssh-ssh1*
ubuntu/openssh-ssh1*
ubuntu/openssh-ssh1*

Event History

Oct 15, 2026
CVE Published
via Ubuntu·12:00 AM
Data Sourced
via Ubuntu·12:00 AM
RemedyDescriptionSeverityAffected Software
Data Sourced
via Red Hat·04:13 AM
DescriptionSeverityAffected Software
CVE Published
via MITRE·01:07 PM
Rejected
via MITRE·01:07 PM
Data Sourced
via OSV·02:17 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·02:17 PM
Description
Oct 21, 2026
Rejected
via MITRE·06:47 AM
Data Sourced
via Microsoft·08:11 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which systems are exposed to this issue?

Systems running OpenSSH sshd with GSSAPIAuthentication enabled are exposed to the credential-storage flaw. RHEL ships with GSSAPIAuthentication enabled, and RHEL 10 defaults GSSAPIDelegateCredentials to enabled.

2

What must occur for delegated credentials to be stored incorrectly?

A client must perform a partial or failed GSSAPI authentication exchange that leaves GSSAPI client state on the connection. If a later authentication attempt succeeds on that same connection, the previously delegated credential may have been stored even though the earlier GSSAPI authorization check did not succeed.

3

Does the leftover GSSAPI state allow an attacker to log in?

No. The RHEL maintainer confirmed that the leftover state does not authorize a later login; the impact is storage of a delegated credential that was not accepted by the user authorization check.

4

What configuration can reduce exposure if patching is not immediately possible?

Disable GSSAPI delegated credentials by setting GSSAPIDelegateCredentials off. On RHEL 10, the credential-storage path returns early when this switch is off.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203