A flaw was found in OpenSSH. With GSSAPI authentication enabled, a failed GSSAPI attempt can leave delegated credentials stored for the connection even though user authorization did not succeed. A later successful login on that connection is not authorized by the leftover state.
This CVE has been withdrawn by MITRE
MITRE marked CVE-2026-110924 as REJECTED on . It is no longer considered a valid vulnerability record. The original content below is preserved for historical reference only.
Reason given by MITRE
CVE-2026-110924 has been marked as a duplicate of CVE-2026-106553.
CVE-2026-110924
✕ Withdrawn — historical dataMEDIUMPre-NVD 4.8
4.8CVSS
- CVSS v3
- 4.8
- EchelonGraph score
- Not yet assessedThis CVE record was withdrawn by its numbering authority, so there is no vulnerability to rate.
- EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- —Not applicable: this CVE ID was withdrawn
Published
October 15, 2026
Last Modified
October 15, 2026
References (2)
- secalert@redhathttps://access.redhat.com/security/cve/CVE-2026-110924
- secalert@redhathttps://bugzilla.redhat.com/show_bug.cgi?id=2553033
Frequently asked(4)
What is CVE-2026-110924?
CVE-2026-110924 is a rejected CVE ID: its record was withdrawn on October 21, 2026 and no longer describes a vulnerability. Reason given: CVE-2026-110924 has been marked as a duplicate of CVE-2026-106553. Its record names CVE-2026-106553 as the replacement.
When was the CVE record for CVE-2026-110924 published?
The CVE record for CVE-2026-110924 was published on October 15, 2026. EchelonGraph's copy of the record carries a last-modified date of October 15, 2026; the record at its source may have been updated since.
What is the CVSS score of CVE-2026-110924?
CVE-2026-110924 has a CVSS base score of 4.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-110924?
There is nothing to remediate under CVE-2026-110924: it is a rejected (withdrawn) CVE ID and no longer describes a vulnerability. Its record names CVE-2026-106553 as the replacement; act on that CVE instead.