CVE-2026-16516
Attack vector
Network
Complexity
Low
Privileges needed
None
User interaction
None
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).
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Reports (0)
Quick answers
- Is CVE-2026-16516 being exploited?
- CVE-2026-16516 is not on CISA's Known Exploited Vulnerabilities list at the time of our last check.
- How severe is CVE-2026-16516?
- It has a CVSS score of 9.0 (CRITICAL) out of 10, according to its public record.
- Where can I read more?
- See the official NVD record.
How sales teams use this
BugzyCRM matches exploited CVEs to companies in your market and drafts a checked email.