Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-16516Published 2026-10-07

CVE-2026-16516 — wolfSSL Inc. wolfSSH

critical (derived)

As of 2026-10-08, CVE-2026-16516 is a Critical-severity (band derived from the CVSS v4.0 score, not stated by the CNA) vulnerability in wolfSSL Inc. wolfSSH, CVSS v4.0 9, EPSS 0.1% (3.6th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-16516, most recently “wolfSSH 1.6.0 patches 5 vulnerabilities incl. critical ECDSA host-key MITM (CVE-2026-16516) and Windows wolfSSHd auth-token reuse (CVE-2026-83540)”.

CVSS v4.0
9/10Critical (derived)
EPSS
0.1%Higher than 3.6% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
1Campaigns referencing it
Priority
4.6/10Threadlinqs triage score
Published
Updated 2026-10-08
CVSS v4.0 9 (Critical, derived from score) · EPSS 0.1% (higher than 3.6% of all scored CVEs) · Priority 4.6/10 · Published 2026-10-07

Last updated:

What is CVE-2026-16516?

wolfSSH does not validate that the ECDSA curve identifier in a KEXDH_REPLY host key blob matches the algorithm negotiated during key exchange. In ParseECCPubKey() (src/internal.c), the blob's algorithm string is used to derive the curve via NameToId/wcPrimeForId without checking against the negotiated ssh->handshake->pubKeyId, and the RFC 5656 curve identifier string is discarded via GetSkip() rather than compared. An active network man-in-the-middle attacker can substitute a host key blob containing a different ECDSA curve, causing the client to import the key on the wrong curve. Because the attacker controls the private key for the substituted curve, signature verification passes. Exploitation requires an active MitM position and a lax public key check callback (e.g., TOFU, algorithm-name-only check, or fingerprint match against the parsed key).

The record classifies CVE-2026-16516 under weakness class CWE-345. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 43 days ago.

Severity and exploitation probability

CVSS v4.0 base score
9 — Critical (derived from score)
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:H/VA:N/SC:L/SI:H/SA:N
EPSS (FIRST)
0.1% probability of exploitation in the next 30 days, higher than 3.6% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
4.6/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-10-07

Is CVE-2026-16516 being exploited?

It currently carries a trending score of 35 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2026-16516

Patch reference: https://github.com/wolfSSL/wolfssh/commit/31d13697a608fa1bf9eec11aa6eff1503ade836f. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2026-16516

1 tracked threat in the Threadlinqs corpus references CVE-2026-16516, either in the campaign’s CVE list or as an indicator on the campaign record.

Sources

Enriched from CVE.org, FIRST EPSS.

Vendor advisory and patch

Issue tracking and product pages