CVE-2026-83742: wolfSSL wolfSSH · Integer Underflow
Affects wolfSSL wolfSSHSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.6.0 when convenient.
Data as of 20 Nov 2026, 17:35 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% 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:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/AU:NExploitation evidence
Disclosed: evidence found.
CVE published 7 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| wolfSSL Inc.wolfSSH | Affected
| Fixed in
|
GitHubwolfSSHpkg:github/wolfSSHOther threats | Affected
| Fixed in
|
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 vulnerable versions (>=1.4.11 <1.6.0) on non-Windows platforms or restrict authenticated user input to prevent crafted SFTP paths that could trigger the overflow. Monitor vendor communications for official fixes.
Description
Unsigned integer underflow in wstrncat() in src/port.c in wolfSSL wolfSSH from v1.4.11 through v1.5.0 on non-Windows platforms allows an authenticated remote attacker to write one out-of-bounds null byte past the end of a stack buffer by sending a crafted SFTP path. wolfSSH_RealPath() in src/ssh.c appends each path component with a remaining-size bound (outSz - curSz) rather than the full destination size, so once the accumulated path reaches half the output buffer the size_t computation n - strlen(s1) - 1 wraps to near SIZE_MAX. The strncat() call is then effectively unbounded and copies the whole component; when that component exactly fills the remainder of the buffer, its terminating null is written one byte past the end. The caller's own length check keeps the copied data inside the buffer, so the overflow is limited to that single null byte, which may corrupt an adjacent stack value and crash the process. Applications that call the public wolfSSH_RealPath() with an output buffer smaller than the input path are additionally exposed to an unbounded copy, because the word32 expression outSz - segSz in that length check also wraps.
References
- github.com/wolfSSL/wolfssh/pull/1084 (opens in a new tab)
- github.com/wolfSSL/wolfssh/commit/822e4464560b467580ea37a2fc03b0988d88b71f (opens in a new tab)
- github.com/wolfSSL/wolfssh/commit/513e52b18927a4e3f7cf17ecaf107958e56139de (opens in a new tab)
- github.com/wolfSSL/wolfssh/commit/fbc7cd88a23b59a45a584020a4c7242d9bd70f35 (opens in a new tab)