Quick answers
- Is CVE-2026-59998 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59998 being exploited in the wild.
- How severe is CVE-2026-59998?
- Medium severity, with a CVSS score of 4.8, published 8 July 2026.
- Which products and versions are affected?
- OpenBSD Openssh before 10.4.
- Is there a fix for CVE-2026-59998?
- A patch was published on 2026-07-06: OpenSSH 10.4 released with fix/documentation update Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-59998 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-59998?
- Check whether you run OpenBSD Openssh at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
In OpenSSH versions prior to 10.4, the 'GSSAPIStrictAcceptorCheck' configuration option in sshd is ineffective when the host is joined to a Windows Active Directory environment. This option is intended to ensure that the GSSAPI acceptor name matches the server's actual hostname, preventing certain types of credential redirection or impersonation. The root cause is an undocumented behavior where the check is bypassed in AD environments. An attacker could potentially exploit this to use a service ticket intended for one host to authenticate to another, provided GSSAPI authentication is enabled. The issue is addressed in OpenSSH 10.4 by updating documentation and/or behavior to reflect this limitation.
Affected products
- OpenBSD OpenSSH before 10.4
Timeline
- 2026-07-06: patched: OpenSSH 10.4 released with fix/documentation update
- 2026-07-08: disclosed: CVE published to NVD