CVE-2025-11933: wofSSL wolfSSL · Improper Input Validation
Affects wofSSL wolfSSLSource CVE Database V5
Not known to be exploited · CVSS 2.3 Low.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:LExploitation evidence
Disclosed: evidence found.
CVE published 21 Nov 2025
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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubwolfssl/wolfsslpkg:github/wolfssl/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
1. Monitor wolfSSL vendor advisories closely and apply security patches or updated versions as soon as they become available to address CVE-2025-11933. 2. In the absence of an immediate patch, implement network-level filtering or intrusion prevention rules to detect and block TLS ClientHello messages containing duplicate CKS extensions. This can be done by enhancing TLS inspection capabilities on firewalls or dedicated security appliances. 3. Conduct an inventory of all devices and applications using wolfSSL, especially embedded and IoT devices, to identify vulnerable versions. 4. Where possible, isolate critical systems using vulnerable wolfSSL versions from untrusted networks to reduce exposure. 5. Employ rate limiting and anomaly detection on TLS handshake traffic to mitigate potential DoS attempts exploiting this vulnerability. 6. Engage with device and application vendors to confirm wolfSSL versions in use and request updates if necessary. 7. Incorporate wolfSSL version checks into vulnerability management and patching workflows to ensure timely remediation. 8. Educate network security teams about this specific TLS extension parsing vulnerability to improve detection and response capabilities.
Description
Improper 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.