Read the docs
TI-2026-68960 Aliases CVE-2026-83742GHSA-4ff8-whrv-3wcm

Integer underflow in wolfSSH lets attackers write past a stack buffer

Priority LOW 24CWE-121Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
—
Confidentiality · integrity · availability
None · Low · Low
Fix status
No fix listed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

wolfSSH from 1.4.11 through 1.5.0 on non-Windows platforms has an unsigned integer underflow in wstrncat() that is reached through wolfSSH_RealPath(). An authenticated remote attacker can send a crafted SFTP path to write one out-of-bounds null byte past the end of a stack buffer (CWE-121). The overflow may corrupt an adjacent stack value and crash the process.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00434 37th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
wolfSSLwolfSSH1.4.11 – 1.5.0—No fix listedCNA
  • wolfSSH VendorwolfSSL Affected 1.4.11 – 1.5.0 Fixed in — No fix listed CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:wolfssh:wolfssh:*:*:*:*:*:*:*:*1.4.11 to before 1.6.0VulnerablewolfSSH
  • cpe:2.3:a:wolfssh:wolfssh:*:*:*:*:*:*:*:* Versions 1.4.11 to before 1.6.0 Vulnerable ·wolfSSH

Remediation

The sources list no fixed version for wolfSSH.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Timeline

  1. 2026-10-07 Threatist record created from CVE-2026-83742
  2. 2026-10-07 Alias added: GHSA-4ff8-whrv-3wcm
  3. 2026-10-07 CISA SSVC decision points changed
  4. 2026-10-13 CVSS score added · NVD

References

  • TI-2024-00830 SEGV and out of bounds memory read from malicious packet CVSS 3.1CRITICAL 9.1
  • TI-2009-04246 Multiple stack-based buffer overflows in the CertDecoder::GetName function in src/asn.cpp… CVSS 2.0HIGH 7.5
  • TI-2022-18557 In wolfSSL before 5.5.1, malicious clients can cause a buffer overflow during a TLS 1.3… CVSS 3.1HIGH 7.5
  • TI-2025-10943 Potential DoS Vulnerability through Multiple KeyShareEntry with Same Group in TLS 1.3 ClientHello CVSS 4.0MEDIUM 6.3
  • TI-2017-09737 wolfSSL Bleichenbacher/ROBOT CVSS 3.0HIGH 7.5
  • TI-2019-08902 wolfSSL 4.0.0 has a Buffer Overflow in DoPreSharedKeys in tls13.c when a current identity… CVSS 3.1CRITICAL 9.8
See all 176 →

Sources