dbcve.org
Openshift Container PlatformApplication · Redhat

CVE-2025-26465

MEDIUM · 6.8 CVSS v3.1 Published 2025-02-18
Fix available
A fix is available. Upgrade to after 9.8 or later.
See remediation →
75/100
Remediation priority · High
Remotely reachable No privileges Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Openshift Container PlatformApplication
Affected:= 4.0
Debian LinuxOperating system
Affected:= 11.0= 12.0
Enterprise LinuxOperating system
Affected:= 9.0
OpensshApplication
Affected:>= 6.9, <= 9.8= 6.8= 9.9
Active Iq Unified ManagerApplication
Affected:all versions
OntapApplication
Affected:= 9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 9.8
Vendor patch ftp.openbsd.org →
Recommended fix Moderate confidence

OpenSSH 9.9 or later (e.g., 9.10, 9.11)

  1. 1. Check current OpenSSH version: ssh -V or sshd -V
  2. 2. Identify the VerifyHostKeyDNS option status in /etc/ssh/ssh_config (should be disabled by default)
  3. 3. For production systems, test upgrade in non-production environment first
  4. 4. Upgrade OpenSSH to version 9.9 or later which contains the fix for CVE-2025-26465
  5. 5. Verify the upgrade: ssh -V to confirm new version
  6. 6. Restart sshd service: systemctl restart sshd
  7. 7. Confirm sshd is running correctly: systemctl status sshd
  8. 8. Test SSH connections to ensure functionality
Caveat Standard upgrade should be low-risk; minor configuration file adjustments may be needed if using non-default VerifyHostKeyDNS settings

Generated from the published advisory — verify against the referenced sources before acting.

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26465 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-26465 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data