Skip to content
Connect AISign inSign up free
CVE-2026-848976.9MediumCWE-372

CVE-2026-84897: wolfSSL Inc. wolfSSH vulnerability

wolfSSL Inc. · wolfSSH

Fixed in Alpine 3.24 · Affected: wolfSSL Inc. wolfSSH · Exploitation: not established

At a glance

0.5%probability of exploitation in the next 30 days
42nd percentile
050100

Higher than 42% of scored CVEs

6.9MediumCVSS 4.0
LowMedium

What it isNVD

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.

Fix status by distribution

From each distribution’s security tracker. Distributions we did not check are not listed.

ExploitationNot established

Not in CISA KEV as of catalogue 2026.11.20 (20 Nov)

  1. Not establishedNothing in the sources we check

Not seen so far: in CISA KEV · exploited (reported) · scanning observed · proof of concept public.

Weakness and public checks

Public check
No public nuclei template
Weakness
Asymmetric Resource Consumption (Amplification) · Denial of Service

Other CVEs in wolfSSH

Every published CVE for wolfSSL Inc. wolfSSH, by how far exploitation has gone. This one is among them.

As a list
Other CVEs in wolfSSH: each mark is one CVE.Drag to move · Ctrl + scroll to zoom · a mark opens that CVE

What changed

Alpine status tracked since 6 Nov 2026.

  1. Seen in Alpine’s tracker on 6 Nov: Alpine 3.24 fixed in wolfssh-1.6.0-r0 Alpine

Coverage1 article · 1 outlet

First in our coverage: SecurityOnline, 8 Oct.

  1. wolfSSH flaw could let attackers pass off forged server keys
    SecurityOnline · first in our coverage · mentions it in passing

New articles also arrive in the RSS feed.

References