CVE-2025-26465: Openssh: machine-in-the-middle attack if verifyhostkeydns is enabled
A vulnerability was found in OpenSSH when the VerifyHostKeyDNS option is enabled. A machine-in-the-middle attack can be performed by a malicious machine impersonating a legit server. This issue occurs due to how OpenSSH mishandles error codes in specific conditions when verifying the host key. For an attack to be considered successful, the attacker needs to manage to exhaust the client's memory resource first, turning the attack complexity high.
Security readout for executives and security teams
Plain-English summary
CVE-2025-26465 can let an attacker impersonate an SSH server when an OpenSSH client has VerifyHostKeyDNS enabled. The impact could expose credentials or session data, but exploitation is constrained by high complexity: sources say the attacker must first exhaust client memory. It is not listed as KEV.
Executive priority
Treat as a moderate-priority infrastructure client update. It is not known exploited in the supplied sources, but it affects trust in SSH server identity and could expose sensitive administrative sessions in the right conditions.
Technical view
OpenSSH mishandles error codes during DNS-based host key verification when VerifyHostKeyDNS is enabled. Under specific memory-exhaustion conditions, this can undermine host key validation and permit a machine-in-the-middle attack. CVSS 3.1 is 6.8 with network attack vector, high complexity, no privileges, user interaction, and high confidentiality and integrity impact.
Likely exposure
Exposure is mainly OpenSSH clients using VerifyHostKeyDNS. The bundle names affected Red Hat openssh packages for RHEL 8, RHEL 9, RHEL 9.4 EUS, Red Hat Discovery 1.14, and Red Hat OpenShift Container Platform 4 rhcos. Other distributions are referenced, but exact affected versions are not fully enumerated here.
Exploitation context
The source bundle does not provide evidence of active exploitation, and KEV is false. Successful attack requires positioning for machine-in-the-middle traffic and first exhausting client memory, making practical exploitation harder. Risk rises where SSH clients rely on DNS host key verification across untrusted networks.
Researcher notes
Focus validation on client-side OpenSSH behavior with VerifyHostKeyDNS enabled. The key constraint is memory exhaustion before host key verification error handling is abused. The source bundle indicates CWE-390 and CVSS AC:H; avoid assuming broad server-side exposure without configuration evidence.
Mitigation direction
Apply applicable vendor security updates from Red Hat, OpenSSH, Debian, Ubuntu, or platform guidance.
Inventory SSH clients and configurations that set VerifyHostKeyDNS to yes.
If VerifyHostKeyDNS is not required, disable it according to approved vendor guidance.
Prioritize updates for administrator workstations, automation runners, and bastion-adjacent clients.
Monitor vendor advisories for affected version clarification and backported fixes.
Validation and detection
Check installed OpenSSH package versions against vendor advisories and errata.
Review ssh_config, included config files, and user configs for VerifyHostKeyDNS.
Confirm patched packages are installed on RHEL 8, RHEL 9, and OpenShift nodes where applicable.
Validate SSH hardening baselines do not depend on vulnerable DNS host key verification behavior.
Document exceptions where patching or configuration changes are deferred.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-390: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
5Timeline events
3ADP providers
25Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-390 · source CWE mapping
Detection of Error Condition Without Action
Detection of Error Condition Without Action represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.