CVE Watchtower

CVE-2026-84897wolfSSL Inc. wolfSSH

NVD

Vulnerability Summary

src/internal.c in wolfSSL wolfSSH through 1.5.0 admits the server-to-client Diffie-Hellman group exchange messages SSH_MSG_KEX_DH_GEX_GROUP (31) and SSH_MSG_KEX_DH_GEX_REPLY (33) when a server receives them from an unauthenticated client. IsMessageAllowedServer() applies no direction check to the key exchange message range: when the peer is keying and no particular message is expected, which is the state a server is in for the whole window after it processes the client's KEXINIT because nothing sets handshake->expectMsgId there, the function falls out of its expectation branch without a verdict and reaches a numeric bound that admits every message id from 30 through 34. A client that negotiates diffie-hellman-group-exchange-sha256 and then sends message 31 makes the server run the client-side handler DoKexDhGexGroup(), which validates the attacker-supplied group with two 8-round Miller-Rabin primality tests, one on p and one on (p-1)/2, on a value of up to 8192 bits. The handler then returns success: the server stores the attacker's prime and generator, generates a Diffie-Hellman key pair in the attacker's group, and sends the client-role message SSH_MSG_KEX_DH_GEX_INIT (32) back to the attacker. Published RFC 3526 safe primes are the worst-case input and cost the attacker nothing to obtain. The primality validation was added in 1.5.0; versions from 1.2.0 through 1.4.22 admit the same message and enter the same client-role path without the primality cost. Message 33 is admitted as well, but on a server it is rejected before any cryptography because no public key check callback is registered, so it carries no comparable cost. Builds that define WOLFSSH_NO_DH_GEX_SHA256, which is implied by WOLFSSH_NO_DH or NO_SHA256, are unaffected.
Severity Level
MEDIUM(6.9)
Published Date
Oct 7, 2026
Last Modified
Oct 7, 2026
Exploitation Status
No confirmed exploitation yet
EPSS Score (30-Day)
0.48%Probability
Root Weakness (CWE)
See the MITRE CWE entry for the full definition of this weakness.
See the MITRE CWE entry for the full definition of this weakness.
The product does not properly control the allocation and maintenance of a limited resource, enabling denial-of-service conditions.
CVSS v4.0 Base Metrics — Score 6.9 (MEDIUM)
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/AU:Y
Attack VectorNetwork
Attack ComplexityLow
Attack RequirementsNone
Privileges RequiredNone
User InteractionNone
Confidentiality (Vulnerable System)None
Integrity (Vulnerable System)None
Availability (Vulnerable System)Low
Confidentiality (Subsequent System)None
Integrity (Subsequent System)None
Availability (Subsequent System)None

Affected & Patched Versions

Affected Versions
  • wolfSSL Inc. wolfSSH >= 1.2.0 and <= 1.5.0
Patched Versions
  • wolfSSL Inc. wolfSSH 1.5.0

What to do

Fix it during your normal patch cycle. No exploitation is confirmed yet.

  1. Check whether you run wolfSSL Inc. wolfSSH and which version.
  2. Update to a patched version listed above, then confirm the new version.

Timeline

  • Oct 7, 2026Published
  • Oct 7, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new wolfSSL Inc. wolfSSH CVEsYou are reading CVE-2026-84897. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

Data last checked: Nov 17, 2026 19:13 UTC