Wolfssl
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in any Wolfssl product.
RSS Feeds for Wolfssl security vulnerabilities
Create a CVE RSS feed including security vulnerabilities found in Wolfssl products with stack.watch. Just hit watch, then grab your custom RSS feed url.
Products by Wolfssl Sorted by Most Security Vulnerabilities since 2018
By the Year
In 2026 there have been 3 vulnerabilities in Wolfssl. Last year, in 2025 Wolfssl had 12 security vulnerabilities published. If vulnerabilities keep coming in at the current rate, it appears that number of security vulnerabilities in Wolfssl in 2026 could surpass last years number.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 3 | 0.00 |
| 2025 | 12 | 0.00 |
| 2024 | 9 | 6.44 |
| 2023 | 1 | 8.80 |
| 2022 | 17 | 6.49 |
| 2021 | 5 | 7.70 |
| 2020 | 6 | 6.37 |
| 2019 | 11 | 9.02 |
| 2018 | 1 | 4.70 |
It may take a day or so for new Wolfssl vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Wolfssl Security Vulnerabilities
| CVE | Date | Vulnerability | Products |
|---|---|---|---|
| CVE-2025-15346 | Jan 07, 2026 |
wolfssl-py <=5.8.2 mTLS bypass CVE-2025-15346A vulnerability in the handling of verify_mode = CERT_REQUIRED in the wolfssl Python package (wolfssl-py) causes client certificate requirements to not be fully enforced. Because the WOLFSSL_VERIFY_FAIL_IF_NO_PEER_CERT flag was not included, the behavior effectively matched CERT_OPTIONAL: a peer certificate was verified if presented, but connections were incorrectly authenticated when no client certificate was provided. This results in improper authentication, allowing attackers to bypass mutual TLS (mTLS) client authentication by omitting a client certificate during the TLS handshake. The issue affects versions up to and including 5.8.2. |
|
| CVE-2025-15382 | Jan 06, 2026 |
CVE-2025-15382: heap overread in wolfSSH CleanPath via crafted SCP pathA heap buffer over-read vulnerability exists in the wolfSSH_CleanPath() function in wolfSSH. An authenticated remote attacker can trigger the issue via crafted SCP path input containing '/./' sequences, resulting in a heap over read by 1 byte. |
|
| CVE-2025-14942 | Jan 06, 2026 |
wolfSSH <1.4.21: KEX State Manupulation Leaks Password & Skips AuthwolfSSHs key exchange state machine can be manipulated to leak the clients password in the clear, trick the client to send a bogus signature, or trick the client into skipping user authentication. This affects client applications with wolfSSH version 1.4.21 and earlier. Users of wolfSSH must update or apply the fix patch and its recommended to update credentials used. This fix is also recommended for wolfSSH server applications. While there arent any specific attacks on server applications, the same defect is present. Thanks to Aina Toky Rasoamanana of Valeo and Olivier Levillain of Telecom SudParis for the report. |
|
| CVE-2025-13912 | Dec 11, 2025 |
wolfSSL <5.8.4 const-time flaw yields timing side-channelMultiple constant-time implementations in wolfSSL before version 5.8.4 may be transformed into non-constant-time binary by LLVM optimizations, which can potentially result in observable timing discrepancies and lead to information disclosure through timing side-channel attacks. |
|
| CVE-2025-12889 | Nov 21, 2025 |
OpenSSL TLS1.2: Client Can Use Weak Digest in CertificateRequestWith TLS 1.2 connections a client can use any digest, specifically a weaker digest that is supported, rather than those in the CertificateRequest. |
|
| CVE-2025-11932 | Nov 21, 2025 |
OpenSSL TLS1.3 PSK binder timing info leak (pre-3.2)The server previously verified the TLS 1.3 PSK binder using a non-constant time method which could potentially leak information about the PSK binder |
|
| CVE-2025-11931 | Nov 21, 2025 |
wolfSSL XChaCha20-Poly1305 Integer Underflow OOBInteger Underflow Leads to Out-of-Bounds Access in XChaCha20-Poly1305 Decrypt. This issue is hit specifically with a call to the function wc_XChaCha20Poly1305_Decrypt() which is not used with TLS connections, only from direct calls from an application. |
|
| CVE-2025-12888 | Nov 21, 2025 |
ESP32 X25519 Timing Side-Channel VulnerabilityVulnerability in X25519 constant-time cryptographic implementations due to timing side channels introduced by compiler optimizations and CPU architecture limitations, specifically with the Xtensa-based ESP32 chips. If targeting Xtensa it is recommended to use the low memory implementations of X25519, which is now turned on as the default for Xtensa. |
|
| CVE-2025-11936 | Nov 21, 2025 |
wolfSSL 5.8.2 TLS1.3 KeyShare DDOS CVE-2025-11936Improper input validation in the TLS 1.3 KeyShareEntry parsing in wolfSSL v5.8.2 on multiple platforms allows a remote unauthenticated attacker to cause a denial-of-service by sending a crafted ClientHello message containing duplicate KeyShareEntry values for the same supported group, leading to excessive CPU and memory consumption during ClientHello processing. |
|
| CVE-2025-11933 | Nov 21, 2025 |
wolfSSL 5.8.2 TLS1.3 CKS Extension Duplicate DoS via Input ValidationImproper Input Validation in the TLS 1.3 CKS extension parsing in wolfSSL 5.8.2 and earlier on multiple platforms allows a remote unauthenticated attacker to potentially cause a denial-of-service via a crafted ClientHello message with duplicate CKS extensions. |
|