Skip to content
VulniPulse
Advisory severityHigh7.7Red Hat Linux

High [CVE-2026-60002] Use-after-free vulnerability during host key re-exchange on the client side

This high-severity Red Hat Linux advisory covers CVE-2026-60002 affecting Red Hat Enterprise Linux 10.0 Extended Update Support, Red Hat Enterprise Linux 9.6 Extended Update Support, Red Hat OpenShift Container Platform 4.22.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-60002 Source published Source updated

VulniPulse record published Record updated

Affected products & platforms
Red Hat LinuxRed Hat Enterprise Linux
Open source advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

ssh in OpenSSH before 10.4 can have a use-after-free when a server changes its host key during a key re-exchange. (This outcome occurs only on the client side.) A flaw was found in OpenSSH. This could lead to high impact on confidentiality and integrity, and low impact on availability.

Red Hat severity: Important — CVSS 7.7 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L). Weakness: CWE-825.

Affected Red Hat products: Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 10.0 Extended Update Support; Red Hat Enterprise Linux 9; Red Hat Enterprise Linux 9.6 Extended Update Support; Red Hat OpenShift Container Platform 4.22; Red Hat Hardened Images; Red Hat Update Infrastructure 5.

Red Hat fixing advisory: RHSA-2026:47757, RHSA-2026:65900, RHSA-2026:47756, RHSA-2026:66410, RHSA-2026:54769, RHSA-2026:37382, RHSA-2026:54387, RHSA-2026:58981.

Affected products named by the advisory: Red Hat package: openssh.

Affected versions
  • < 10.4

Official advisory · high-confidence parse· fetched 17 days ago·verify at source

Fixed versions
  • openssh-0:9.9p1-25.el10_2
  • openssh-0:9.9p1-7.el10_0.4
  • openssh-0:9.9p1-9.el9_8
  • openssh-0:8.7p1-45.el9_6.4
  • rhcos-4.22.9.8.202608130832-0
  • openssh-main-10.4p1-1.hum1
  • rhui5/installer-rhel9:1786435483
  • rhui5/rhua-rhel9:1786533529
  • rhui5/installer-tp-rhel9:1787135742
  • rhui5/rhua-tp-rhel9:1787241260
  • RHSA-2026:47757
  • RHSA-2026:65900
  • RHSA-2026:47756
  • RHSA-2026:66410
  • RHSA-2026:54769
  • RHSA-2026:37382
  • RHSA-2026:54387
  • RHSA-2026:58981

Official advisory · high-confidence parse· fetched 17 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • To mitigate this issue, OpenSSH clients should only connect to trusted SSH servers. Enforcing strict host key checking and carefully managing `known_hosts` files can help prevent connections to servers with unexpected or altered host keys, thereby reducing exposure to this client-side vulnerability.

Official advisory · high-confidence parse· fetched 17 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.