# CVE-2026-60002: Use after free in OpenSSH > A use-after-free in the OpenSSH client allows attackers to cause denial of service or execute code during key re-exchange. - **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 8 Jul 2026 - **Updated:** 8 Jul 2026 - **Also known as:** ALPINE-CVE-2026-60002, AZL-92054, BELL-CVE-2026-60002, CLSA-2026-1784109248, DEBIAN-CVE-2026-60002, ECHO-f3c1-98db-8b17, GHSA-gp5v-jg37-fvg6, JLSEC-2026-1326, OESA-2026-3565, OESA-2026-3566, OESA-2026-3567, OESA-2026-3568, RHSA-2026:65900, RHSA-2026:66410, ROOT-OS-DEBIAN-11-CVE-2026-60002, ROOT-OS-DEBIAN-12-CVE-2026-60002, ROOT-OS-DEBIAN-13-CVE-2026-60002, UBUNTU-CVE-2026-60002 ## What is CVE-2026-60002? CVE-2026-60002 is a high-severity use after free vulnerability in OpenSSH, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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.) Weakness: CWE-416 (Use After Free) ## Which versions are affected by CVE-2026-60002? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `openssh` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:9.9p1-7.el10_0.4 | | `openssh-askpass` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:9.9p1-7.el10_0.4 | | `openssh-askpass-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:9.9p1-7.el10_0.4 | | `openssh-clients` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:9.9p1-7.el10_0.4 | | `openssh-clients-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:9.9p1-7.el10_0.4 | | `openssh-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:9.9p1-7.el10_0.4 | | `openssh-debugsource` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:9.9p1-7.el10_0.4 | | `openssh-keycat` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:9.9p1-7.el10_0.4 | | `openssh-keycat-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:9.9p1-7.el10_0.4 | | `openssh-keysign` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:9.9p1-7.el10_0.4 | | `openssh-keysign-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:9.9p1-7.el10_0.4 | | `openssh-server` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:9.9p1-7.el10_0.4 | | `openssh-server-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:9.9p1-7.el10_0.4 | | `openssh-askpass` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:8.7p1-45.el9_6.4 | | `openssh-askpass-debuginfo` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:8.7p1-45.el9_6.4 | | `openssh-debuginfo` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:8.7p1-45.el9_6.4 | | `openssh-debugsource` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:8.7p1-45.el9_6.4 | | `openssh-keycat-debuginfo` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:8.7p1-45.el9_6.4 | | `openssh-server-debuginfo` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:8.7p1-45.el9_6.4 | | `openssh-sk-dummy-debuginfo` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:8.7p1-45.el9_6.4 | | `pam_ssh_agent_auth` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:0.10.4-5.45.el9_6.4 | | `openssh` | Red Hat:rhel_eus:9.6::baseos | All versions | 0:8.7p1-45.el9_6.4 | | `openssh-askpass-debuginfo` | Red Hat:rhel_eus:9.6::baseos | All versions | 0:8.7p1-45.el9_6.4 | | `openssh-clients` | Red Hat:rhel_eus:9.6::baseos | All versions | 0:8.7p1-45.el9_6.4 | | `openssh-debuginfo` | Red Hat:rhel_eus:9.6::baseos | All versions | 0:8.7p1-45.el9_6.4 | | `openssh-debugsource` | Red Hat:rhel_eus:9.6::baseos | All versions | 0:8.7p1-45.el9_6.4 | | `openssh-keycat` | Red Hat:rhel_eus:9.6::baseos | All versions | 0:8.7p1-45.el9_6.4 | | `openssh-keycat-debuginfo` | Red Hat:rhel_eus:9.6::baseos | All versions | 0:8.7p1-45.el9_6.4 | | `openssh-server` | Red Hat:rhel_eus:9.6::baseos | All versions | 0:8.7p1-45.el9_6.4 | | `openssh-server-debuginfo` | Red Hat:rhel_eus:9.6::baseos | All versions | 0:8.7p1-45.el9_6.4 | | `openssh-sk-dummy-debuginfo` | Red Hat:rhel_eus:9.6::baseos | All versions | 0:8.7p1-45.el9_6.4 | Products: OpenSSH. ## How do I fix CVE-2026-60002? Upgrade to a fixed version. ## Is CVE-2026-60002 being exploited? There is no known exploitation of CVE-2026-60002 in the wild and no public exploit code. ## Other vulnerabilities in OpenSSH - [CVE-2003-0786](https://insights.sbomify.com/CVE-2003-0786/): Auth bypass in n/a (critical 10.0) - [CVE-2003-0693](https://insights.sbomify.com/CVE-2003-0693/): Memory corruption in n/a (critical 10.0) - [CVE-2002-0640](https://insights.sbomify.com/CVE-2002-0640/): Memory corruption in n/a (critical 10.0) - [CVE-2001-0144](https://insights.sbomify.com/CVE-2001-0144/): Integer overflow in n/a (critical 10.0) - [CVE-2000-0999](https://insights.sbomify.com/CVE-2000-0999/): Memory corruption in n/a (critical 10.0) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-60002 and fix it if it is affected. What it is: CVE-2026-60002 is a high-severity use after free vulnerability in OpenSSH, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-60002 in the wild and no public exploit code. Affected product: OpenSSH. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-60002/ (Markdown: https://insights.sbomify.com/CVE-2026-60002/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-60002 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-60002 - OSV: https://osv.dev/vulnerability/CVE-2026-60002 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-60002/ Summaries are generated and may contain mistakes; the official description above is the record.