Date: October 6, 2026 Severity: High Affected Users: Operators of wolfSSHd on Windows, wolfSSH versions 1.4.15 through 1.5.0. Non-Windows builds are not affected. Fixed In: wolfSSH v1.6.0 (PR 1163) Summary On Windows, wolfSSHd used a single authentication context, and the logon token stored in it, for every concurrent connection. A user with a valid account […]
Read MoreMore TagCategory: wolfSSH
Vulnerability Disclosure: wolfSSH (CVE-2026-83742)
Date: October 6, 2026 Severity: Medium Affected Users: Servers and applications using wolfSSH versions 1.4.11 through 1.5.0 on non-Windows platforms. Applications that call wolfSSH_RealPath() directly are additionally exposed (see below). Fixed In: wolfSSH v1.6.0 (PR 1084) Summary wolfSSH_RealPath() could be driven to write one byte past the end of a stack buffer. A crafted SFTP […]
Read MoreMore TagVulnerability Disclosure: wolfSSH (CVE-2026-84897)
Date: October 6, 2026 Severity: Medium Affected Users: Operators of wolfSSH servers, wolfSSH versions 1.2.0 through 1.5.0. Builds with WOLFSSH_NO_DH_GEX_SHA256 defined are not affected. Fixed In: wolfSSH v1.6.0 (PR 1221) Summary A wolfSSH server accepted two key exchange messages that only a server should ever send. An unauthenticated client could use one of them to […]
Read MoreMore TagVulnerability Disclosure: wolfSSH (CVE-2026-81535)
Date: October 6, 2026 Severity: Medium Affected Users: Applications built with –enable-fwd (port forwarding), wolfSSH versions 1.4.8 through 1.5.0. Fixed In: wolfSSH v1.6.0 (PR 1059, 1148, 1220) Summary With forwarding enabled, wolfSSH admitted forwarded-tcpip channel opens without consulting the application’s forwarding policy callback, and a client accepted them for forwards it had never requested. A […]
Read MoreMore TagVulnerability Disclosure: wolfSSH (CVE-2026-16516)
Date: October 6, 2026 Severity: Critical Affected Users: Applications using the wolfSSH client with wolfSSH releases through v1.5.0 that rely on ECDSA host keys. Fixed In: wolfSSH v1.6.0 (PR 1022, issue #1012) Summary A man-in-the-middle could substitute a server’s ECDSA host key with a key on a different curve and still pass signature verification, using […]
Read MoreMore TagwolfSSH v1.6.0 Release
wolfSSH v1.6.0 is now available. This release has five vulnerability fixes, strict key exchange enabled by default, ML-DSA host keys and user authentication, and the largest hardening pass wolfSSH has had. Several defaults have changed, so please read the Behavior Changes section before upgrading. See the ChangeLog.md for the full list. Vulnerabilities This release addresses […]
Read MoreMore TagwolfSSH now supports X.509 host certificates with TPM-backed keys: Certificate-based host authentication with private keys sealed in hardware
The problem When an SSH client connects to a server, it needs to know it is talking to the real server and not an attacker in the middle. Classic SSH handles this with a raw host key that the client remembers on first connection. That works for a single machine, but it does not scale […]
Read MoreMore TagSSH Host Keys That Never Leave the TPM with wolfSSH and wolfTPM
Many embedded devices generate their SSH server host key in RAM on every boot, then hand it to the SSH stack as a DER buffer. It works, but the private key lives in memory where firmware bugs, cold-boot attacks, or a careless core dump can leak it. For a safety-critical or long-lived product, the host […]
Read MoreMore TagwolfSSH Continues on the Post-Quantum Hybrid Key Exchange Journey
Go checkout the master branch of wolfSSH. Two new hybrid KEX methods have been added. Both are defined in draft-ietf-sshm-mlkem-hybrid-kex: mlkem768x25519-sha256 — ML-KEM-768 paired with X25519 mlkem1024nistp384-sha384 — ML-KEM-1024 paired with NIST P-384 This joins mlkem768nistp256-sha256 which has been there for a long time. Why hybrid The “harvest now, decrypt later” threat model means ciphertext […]
Read MoreMore TagTLS vs. SSH: When To Use Which (2026 Edition)
TLS and SSH are both widely used protocols for creating secure connections between two systems over an untrusted network. Although they share some fundamental goals, they are designed for different use cases. In this updated guide, we will explore when you should use which, along with a look at the latest developments in both protocols. […]
Read MoreMore Tag