CVE-2025-15346: wolfSSL-py · Missing Authentication
Affects wolfSSL-pySource CVE Database V5
Not known to be exploited · CVSS 9.3 Critical.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/AU:YExploitation evidence
Disclosed: evidence found.
CVE published 7 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| wolfSSLwolfSSL-py | Affected
| Fixed in– |
PyPIwolfssl-pypkg:pypi/wolfssl-pyOther threats | Affected
| Fixed in– |
PyPIwolfsslpkg:pypi/wolfsslOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2025-15346, organizations should: 1) Immediately audit their use of wolfSSL-py to identify affected versions (up to 5.8.2). 2) Apply patches or upgrade to a fixed version once released by wolfSSL; monitor vendor advisories closely. 3) As an interim measure, implement additional application-layer checks to enforce client certificate presence and validity beyond wolfSSL-py's built-in verification. 4) Configure TLS settings to explicitly include the WOLFSSL_VERIFY_FAIL_IF_NO_PEER_CERT flag or equivalent to ensure strict client certificate enforcement. 5) Employ network-level controls such as mutual TLS termination proxies that enforce client authentication independently. 6) Conduct penetration testing and validation of mTLS configurations to confirm that client certificates are mandatory and properly verified. 7) Monitor logs for unexpected connections lacking client certificates and investigate anomalies. 8) Educate developers and security teams about the importance of correct TLS flag usage and secure library configurations. These steps go beyond generic TLS hardening by focusing on wolfSSL-py specific configuration and compensating controls.
Description
A 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.