NVD / CVE Program· CNA mitre

CVE-2026-60002: ssh in OpenSSH before 10.4 can have a use-after-free when a server changes its host key during a key re-exchange.

Noroxi assessment

Priority: Monitor (action score 37/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.30% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: azl3 openssh 9.8p1-8 on Azure Linux 3.0 9.8p1-9.

Low priority for now. Upgrade to azl3 openssh 9.8p1-8 on Azure Linux 3.0 9.8p1-9 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.)

CriticalCVSS 9.4 · v3.1—No exploit Fix available

Published: Jul 8, 2026
Updated: Oct 25, 2026
EPSS: 0.3% · 22th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 37 / 40 · 9.4 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 9.4
CNA · mitre: 7.7; 1.7 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
openbsd	openssh	cpe:2.3:a:openbsd:openssh

Is OpenSSH on your server exposed to the internet?

The free port scanner finds the open ports on your server and matches the service versions it can read against known vulnerabilities. No account needed.

Run a port scan

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

openbsd opensshbefore 10.4

Versions reported by the vendor

Affected version ranges reported by the assigning authority (mitre). Independent of NVD's CPE analysis and usually ahead of it.

OpenBSD OpenSSH
- before 10.4affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
AlmaLinux:10	openssh	before 9.9p1-25.el10_2.alma.1	9.9p1-25.el10_2.alma.1
AlmaLinux:10	openssh-askpass	before 9.9p1-25.el10_2.alma.1	9.9p1-25.el10_2.alma.1
AlmaLinux:10	openssh-clients	before 9.9p1-25.el10_2.alma.1	9.9p1-25.el10_2.alma.1
AlmaLinux:10	openssh-keycat	before 9.9p1-25.el10_2.alma.1	9.9p1-25.el10_2.alma.1
AlmaLinux:10	openssh-keysign	before 9.9p1-25.el10_2.alma.1	9.9p1-25.el10_2.alma.1
AlmaLinux:10	openssh-server	before 9.9p1-25.el10_2.alma.1	9.9p1-25.el10_2.alma.1
AlmaLinux:9	openssh	before 9.9p1-9.el9_8.alma.1	9.9p1-9.el9_8.alma.1
AlmaLinux:9	openssh-askpass	before 9.9p1-9.el9_8.alma.1	9.9p1-9.el9_8.alma.1
AlmaLinux:9	openssh-clients	before 9.9p1-9.el9_8.alma.1	9.9p1-9.el9_8.alma.1
AlmaLinux:9	openssh-keycat	before 9.9p1-9.el9_8.alma.1	9.9p1-9.el9_8.alma.1
AlmaLinux:9	openssh-server	before 9.9p1-9.el9_8.alma.1	9.9p1-9.el9_8.alma.1
AlmaLinux:9	pam_ssh_agent_auth	before 0.10.4-7.9.el9_8.alma.1	0.10.4-7.9.el9_8.alma.1
Alpine:v3.24	openssh	before 10.3_p1-r1	10.3_p1-r1
Debian:12	openssh	from 0	—
Debian:14	openssh	before 1:10.4p1-1	1:10.4p1-1
openSUSE:Leap 16.0	openssh	before 10.0p2-160000.7.1	10.0p2-160000.7.1
openSUSE:Leap 16.0	openssh-askpass-gnome	before 10.0p2-160000.7.1	10.0p2-160000.7.1
Red Hat:enterprise_linux_eus:10.0	openssh	before 0:9.9p1-7.el10_0.4	0:9.9p1-7.el10_0.4
Red Hat:enterprise_linux_eus:10.0	openssh-askpass	before 0:9.9p1-7.el10_0.4	0:9.9p1-7.el10_0.4
Red Hat:enterprise_linux_eus:10.0	openssh-askpass-debuginfo	before 0:9.9p1-7.el10_0.4	0:9.9p1-7.el10_0.4
Red Hat:enterprise_linux_eus:10.0	openssh-clients	before 0:9.9p1-7.el10_0.4	0:9.9p1-7.el10_0.4
Red Hat:enterprise_linux_eus:10.0	openssh-clients-debuginfo	before 0:9.9p1-7.el10_0.4	0:9.9p1-7.el10_0.4
Red Hat:enterprise_linux_eus:10.0	openssh-debuginfo	before 0:9.9p1-7.el10_0.4	0:9.9p1-7.el10_0.4
Red Hat:enterprise_linux_eus:10.0	openssh-debugsource	before 0:9.9p1-7.el10_0.4	0:9.9p1-7.el10_0.4

+63

Same product

openbsd: all records

Other highest-scoring records for the same primary product.

CVE-2023-38408The PKCS#11 feature in ssh-agent in OpenSSH before 9.3p2 has an insufficiently trustworthy search path, leading to remote code execution if
63This week
CVE-2018-15473OpenSSH through 7.7 is prone to a user enumeration vulnerability due to not delaying bailout for an invalid authenticating user until after
60This week
CVE-2016-6210sshd in OpenSSH before 7.3, when SHA256 or SHA512 are used for user password hashing, uses BLOWFISH hashing on a static password when the us
60This week

Published before and after this one in the same product

← EarlierCVE-2026-60000Jul 8, 2026 · sshd in OpenSSH before 10.4 allows remote attackers to cause a denial of service (resource consumption from excessive authentication attempt
30Monitor
← EarlierCVE-2026-60001Jul 8, 2026 · sshd in OpenSSH before 10.4 does not always honor the minimum authentication delay.
26Monitor
Later →CVE-2026-73281Aug 11, 2026 · In ssh-agent in OpenSSH before 10.5, some operations can occur remotely but were intended to occur only locally, including operations that a
14Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
azl3 openssh 9.8p1-8 on Azure Linux 3.0	9.8p1-9 · CBL-Mariner Releases	Microsoft (MSRC)
almalinux:openssh	9.9p1-9.el9_8.alma.1 · AlmaLinux:9	Package registry (OSV)
almalinux:openssh-askpass	9.9p1-9.el9_8.alma.1 · AlmaLinux:9	Package registry (OSV)
almalinux:openssh-clients	9.9p1-9.el9_8.alma.1 · AlmaLinux:9	Package registry (OSV)
almalinux:openssh-keycat	9.9p1-9.el9_8.alma.1 · AlmaLinux:9	Package registry (OSV)
almalinux:openssh-keysign	9.9p1-25.el10_2.alma.1 · AlmaLinux:10	Package registry (OSV)
almalinux:openssh-server	9.9p1-9.el9_8.alma.1 · AlmaLinux:9	Package registry (OSV)
almalinux:pam_ssh_agent_auth	0.10.4-7.9.el9_8.alma.1 · AlmaLinux:9	Package registry (OSV)
alpine:openssh	10.3_p1-r1 · Alpine:v3.24	Package registry (OSV)
debian:openssh	1:10.4p1-1 · Debian:14	Package registry (OSV)
opensuse:openssh	10.0p2-160000.7.1 · openSUSE:Leap 16.0	Package registry (OSV)
opensuse:openssh-askpass-gnome	10.0p2-160000.7.1 · openSUSE:Leap 16.0	Package registry (OSV)
red hat:openssh	0:10.4p1-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:openssh-askpass	0:10.4p1-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:openssh-askpass	0:9.9p1-9.el9_8 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:openssh-askpass-debuginfo	0:9.9p1-9.el9_8 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:openssh-clients	0:10.4p1-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:openssh-clients	0:9.9p1-9.el9_8 · Red Hat:enterprise_linux:9::baseos	Package registry (OSV)
red hat:openssh-clients-debuginfo	0:9.9p1-9.el9_8 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:openssh-debuginfo	0:9.9p1-9.el9_8 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:openssh-debugsource	0:9.9p1-9.el9_8 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:openssh-keycat	0:10.4p1-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:openssh-keycat-debuginfo	0:9.9p1-9.el9_8 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:openssh-keysign	0:10.4p1-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:openssh-server	0:10.4p1-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:openssh-server-debuginfo	0:9.9p1-9.el9_8 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:openssh-sk-dummy	0:10.4p1-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:openssh-sk-dummy-debuginfo	0:9.9p1-9.el9_8 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:pam_ssh_agent_auth	0:0.10.4-7.9.el9_8 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:pam_ssh_agent_auth-debuginfo	0:0.10.4-7.9.el9_8 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-7328234 days apartIn ssh in OpenSSH before 10.5, a use-after-free for realloc data can occur if a certain pair of remote-forwarding operations are concurrent.
19Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: low · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: Low

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:45 PM UTC

For records you follow, these changes also arrive as notifications. →

References

marc.info/?l=openssh-unix-dev&m=178333966933090&w=2

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records