CVE-2026-81535Wolfssh · Wolfssh
Vulnerability data via NVD (ingested)
In wolfSSH through 1.5.0 built with --enable-fwd, DoChannelOpen() in src/internal.c gates only direct-tcpip channel opens with the forwarding policy callback. forwarded-tcpip opens are admitted without an authorization check and are not capped in number, allowing a malicious SSH peer to make an endpoint allocate unbounded per-channel buffers for forwarding channels the application never authorized. A client also does not check a forwarded-tcpip open against the forwards it registered with a tcpip-forward request, as RFC 4254 section 7.2 requires, so a malicious server can open forwarding channels for addresses and ports the client never asked it to forward.
External references
Search for exposed instances
Shodan + Censys queries derived from NVD's CPE data. The vuln tag catches assets Shodan has explicitly linked to this CVE; the product / banner fingerprints find exposed instances even when the vuln tag was never applied (which is common).
vuln:CVE-2026-81535product:"Wolfssh Wolfssh"http.html:"Wolfssh"More intel sources (5)
vuln:CVE-2026-81535vulnerabilities.cve_id: CVE-2026-81535CVE-2026-81535CVE-2026-81535"CVE-2026-81535" exploit -site:nvd.nist.gov