Service interruption via duplicate CKS extensions
Published Nov 21, 2025 · Updated Nov 21, 2025
Improper input validation in wolfSSL 3.12.0 through 5.8.3 allows remote attackers to leak memory via duplicate CKS extensions. TLSX_Parse omitted TLSX_CKS from its duplicate-extension rejection set, so repeated CKS entries in a TLS 1.3 ClientHello were processed and leaked allocations. The server build must include CKS support and receive the crafted handshake; repeated requests can deplete memory and interrupt the hosting process.
Summary
What happened
Improper input validation in wolfSSL 3.12.0 through 5.8.3 allows remote attackers to leak memory via duplicate CKS extensions. TLSX_Parse omitted TLSX_CKS from its duplicate-extension rejection set, so repeated CKS entries in a TLS 1.3 ClientHello were processed and leaked allocations. The server build must include CKS support and receive the crafted handshake; repeated requests can deplete memory and interrupt the hosting process.
The record
- CVE
- CVE-2025-11933
- Published
- Nov 21, 2025
- Updated
- Nov 21, 2025
- Vendor
- wolfSSL
- Product
- wolfSSL
- Classifications
- CWE-20, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 21, 2025CVE publishedPublication date reported by the CVE source.
- Nov 21, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=v5.8.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo