# CVE-2026-81535 — wolfSSL Inc. wolfSSH

> As of 2026-10-08, CVE-2026-81535 is a Medium-severity (band derived from the CVSS v4.0 score, not stated by the CNA) vulnerability in wolfSSL Inc. wolfSSH, CVSS v4.0 6.3, EPSS 0.2% (18.4th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-81535, most recently “wolfSSH 1.6.0 patches 5 vulnerabilities incl. critical ECDSA host-key MITM (CVE-2026-16516) and Windows wolfSSHd auth-token reuse (CVE-2026-83540)”.

**Last updated:** 2026-10-08

## What is CVE-2026-81535?

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.

The record classifies CVE-2026-81535 under weakness classes [CWE-862](https://intel.threadlinqs.com/cwe/CWE-862), [CWE-863](https://intel.threadlinqs.com/cwe/CWE-863). 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 43 days ago.

## Severity and exploitation probability

- **CVSS v4.0 base score:** 6.3 — Medium (derived from score) (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **EPSS (FIRST):** 0.2% probability of exploitation in the next 30 days, higher than 18.4% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 3.9/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-10-07

## Is CVE-2026-81535 being exploited?

It currently carries a trending score of 39 in the Threadlinqs vulnerability feed.

## Affected products and versions

- [wolfSSL Inc.](https://intel.threadlinqs.com/vendors/wolfssl): wolfSSH

## How to fix CVE-2026-81535

Patch reference: [https://github.com/wolfSSL/wolfssh/commit/616eb681e70759c30c3ba158f2b18d7bd954def8](https://github.com/wolfSSL/wolfssh/commit/616eb681e70759c30c3ba158f2b18d7bd954def8). Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

## Threat activity tracking CVE-2026-81535

1 tracked threat in the Threadlinqs corpus references CVE-2026-81535, either in the campaign’s CVE list or as an indicator on the campaign record.

- [wolfSSH 1.6.0 patches 5 vulnerabilities incl. critical ECDSA host-key MITM (CVE-2026-16516) and Windows wolfSSHd auth-token reuse (CVE-2026-83540)](https://intel.threadlinqs.com/threat/TL-2026-3044) — CRITICAL · 2026-10-08

## Sources

Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com — patch](https://github.com/wolfSSL/wolfssh/commit/616eb681e70759c30c3ba158f2b18d7bd954def8)
- [github.com — patch (e396a0a4b6b367f10270287446a4be0071742b5c)](https://github.com/wolfSSL/wolfssh/commit/e396a0a4b6b367f10270287446a4be0071742b5c)
- [github.com — patch (79a7f299337a28aa561409688a268d0efe6e295c)](https://github.com/wolfSSL/wolfssh/commit/79a7f299337a28aa561409688a268d0efe6e295c)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-81535
Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Sign up free (Blue): https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
