CVE-2026-106553

Analyzed Analyzed - Analysis Complete

BaseFortify

Publication date: 2026-10-06

Last updated on: 2026-10-13

Assigner: MITRE

Description

In sshd in OpenSSH before 10.6, credentials can incorrectly persist after failure of a GSSAPIAuthentication authentication attempt.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-10-06

Last Modified

2026-10-13

Generated

2026-10-19

AI Q&A

2026-10-07

EPSS Evaluated

2026-10-18

NVD

CVE-2026-106553

Affected Vendors & Products

Vendor	Product	Version / Range
openbsd	openssh	to 10.6 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-669	The product does not properly transfer a resource/behavior to another sphere, or improperly imports a resource/behavior from another sphere, in a manner that provides unintended control over that resource.

Attack-Flow Graph

Executive Summary

This vulnerability in OpenSSH before version 10.6 allows user credentials to remain active even after a failed GSSAPIAuthentication attempt. This means an attacker could potentially gain unauthorized access despite failing authentication.

Detection Guidance

This vulnerability involves credentials persisting after a failed GSSAPIAuthentication attempt in OpenSSH. To detect it, check OpenSSH version with 'ssh -V' and compare against 10.6. Inspect logs for failed GSSAPI attempts in /var/log/auth.log or similar. Verify credential persistence by testing multiple authentication attempts.

Impact Analysis

If you use OpenSSH with GSSAPI authentication, an attacker might exploit this flaw to maintain access to your system even after failing authentication. This could lead to unauthorized control or data access.

Compliance Impact

This vulnerability could lead to unauthorized access, violating data protection requirements in GDPR and HIPAA. Non-compliance may result in legal penalties or data breaches.

Mitigation Strategies

Upgrade OpenSSH to version 10.6 or later to address the credential persistence issue in GSSAPIAuthentication.

Hi! I’m here to help you understand CVE-2026-106553. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70