CVE-2026-84897
CVE-2026-84897 is a medium-severity vulnerability in Wolfssh with a CVSS 3.x base score of 5.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-372.
Key facts
- Severity: Medium (CVSS 3.x base score 5.3)
- CVSS v4: 6.9
- EPSS exploit prediction: 0% (42nd percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-372
- Affected product: Wolfssh
- Published:
- Last modified:
Description
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.
Frequently asked questions
- What is CVE-2026-84897?
- 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.
- How severe is CVE-2026-84897?
- CVE-2026-84897 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability low.
- Is CVE-2026-84897 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (42nd percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2026-84897?
- CVE-2026-84897 affects Wolfssh. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2026-84897?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- When was CVE-2026-84897 published?
- CVE-2026-84897 was published on 2026-10-07 and last updated on 2026-10-13.
References
- https://github.com/wolfSSL/wolfssh/commit/a472f1ee2b653f623d85ef2297321733f1dbfd22
- https://github.com/wolfSSL/wolfssh/pull/1221
- https://www.rfc-editor.org/rfc/rfc3526.html
- https://www.rfc-editor.org/rfc/rfc4419.html
Affected products (1)
- cpe:2.3:a:wolfssh:wolfssh:*:*:*:*:*:*:*:*
More vulnerabilities in Wolfssh
- CVE-2025-14942 — Critical (CVSS 9.8): wolfSSH’s key exchange state machine can be manipulated to leak the client’s password in the clear, trick the…
- CVE-2025-11625 — Critical (CVSS 9.8): Improper host authentication vulnerability in wolfSSH version 1.4.20 and earlier clients that allows authentication…
- CVE-2025-11624 — Critical (CVSS 9.8): Potential stack buffer overwrite on the SFTP server side when receiving a malicious packet that has a handle size…
- CVE-2022-32073 — Critical (CVSS 9.8): WolfSSH v1.4.7 was discovered to contain an integer overflow via the function wolfSSH_SFTP_RecvRMDIR.
- CVE-2026-81535 — Critical (CVSS 9.1): In wolfSSH through 1.5.0 built with --enable-fwd, DoChannelOpen() in src/internal.c gates…
- CVE-2024-2873 — Critical (CVSS 9.1): A vulnerability was found in wolfSSH's server-side state machine before versions 1.4.17. A malicious client could…
Other CWE-372 vulnerabilities
- CVE-2024-22590 — Critical (CVSS 9.1): The TLS engine in Kwik commit 745fd4e2 does not track the current state of the connection. This vulnerability can allow…
- CVE-2023-4012 — High (CVSS 7.5): ntpd will crash if the server is not NTS-enabled (no certificate) and it receives an NTS-enabled client request (mode…
- CVE-2020-27222 — High (CVSS 7.5): In Eclipse Californium version 2.3.0 to 2.6.0, the certificate based (x509 and RPK) DTLS handshakes accidentally fails,…
- CVE-2026-57893 — Medium (CVSS 6.8): Incomplete internal state distinction in the MigTD's SPDM responder for the Intel(R) TDX Migration Trust Domain (MigTD)…
- CVE-2026-41388 — Medium (CVSS 6.5): OpenClaw before 2026.3.31 contains a configuration management vulnerability where startup migration treats empty-array…
- CVE-2026-41340 — Medium (CVSS 6.5): OpenClaw before 2026.3.31 contains an authentication boundary vulnerability where Telegram legacy allowFrom migration…