Skip to main content
VulnerabilityPublished

CVE-2026-83540: wolfSSL wolfSSH · Improper Authentication

Affects wolfSSL wolfSSHSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.7 High : upgrade to 1.6.0 soon.

Data as of 20 Nov 2026, 17:35 UTC

CVSS 4.0 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.6.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade wolfSSL wolfSSH to 1.6.0.

Affected software

ProductAffectedFixed in
wolfSSLwolfSSHAffected
  • >=1.4.15 <1.6.0
Fixed in
  • 1.6.0
GitHubwolfSSHpkg:github/wolfSSHOther threatsAffected
  • >=1.4.15 <1.6.0
Fixed in
  • 1.6.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, avoid using the Windows port of wolfSSHd in sensitive environments or restrict access to trusted users only.

Description

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.

References

Community reviews

Loading reviews…