CVE-2026-81535: wolfSSL Inc. wolfSSH vulnerability
wolfSSL Inc. · wolfSSH
Fixed in Alpine 3.24 · Affected: wolfSSL Inc. wolfSSH · Exploitation: not established
At a glance
Higher than 23% of scored CVEs
What it isNVD
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.
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
- Missing Authorization · Access Control
Other CVEs in wolfSSH
Every published CVE for wolfSSL Inc. 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.