CVE-2026-83540: wolfSSL wolfSSH vulnerability
wolfSSL · wolfSSH
Fixed in Alpine 3.24 · Affected: wolfSSL wolfSSH · Exploitation: not established
At a glance
Higher than 47% of scored CVEs
What it isNVD
When password or public key authentication is used with the Windows port of wolfSSHd, the Windows logon token acquired for one authenticated connection is not released before a token is acquired for a subsequent connection, resulting in user login poisoning between connections.
A less privileged user with a valid account on the server can exploit this to force a login as a more privileged user. The vulnerability was introduced with the initial Windows port of wolfSSHd in wolfSSH version 1.4.15 and affects all versions through 1.5.0. Non-Windows builds of wolfSSHd are not affected.
Fix status by distribution
From each distribution’s security tracker. Distributions we did not check are not listed.
- Alpine Linux 3.24Fixed in wolfssh-1.6.0-r0checked 21 Nov 20:00 UTC
ExploitationNot established
Not in CISA KEV as of catalogue 2026.11.20 (20 Nov)
- 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
- Improper Authentication · Authentication
Other CVEs in wolfSSH
Every published CVE for wolfSSL wolfSSH, by how far exploitation has gone. This one is among them.
What changed
Alpine status tracked since 6 Nov 2026.
- 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.
- wolfSSH flaw could let attackers pass off forged server keysSecurityOnline · first in our coverage · mentions it in passing
New articles also arrive in the RSS feed.