CVE Catalog

CVE-2026-81535

MediumCVSS 6.3
Published: Translated: NVD NIST

Summary

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.

Risk Assessment

A malicious SSH peer can cause uncontrolled memory and resource consumption, leading to resource exhaustion and potential denial of service, and can open unauthorized forwarding channels, violating security policy.

Recommendation

Update wolfSSH to a patched version and consider disabling the --enable-fwd option if not required to reduce the risk of unauthorized forwarding.

Other vulnerabilities in wolfSSH

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS