Server resource exhaustion via duplicate KeyShare entries
Published Nov 21, 2025 · Updated Dec 8, 2025
Improper input validation in wolfSSL 3.12.0 through 5.8.3 allows remote attackers to exhaust server resources with a TLS 1.3 ClientHello. The KeyShareEntry parser accepts repeated entries for the same supported group and allocates new key-share state without releasing the prior allocation. Only server-side TLS 1.3 processing is exposed; repeated unauthenticated handshakes consume CPU and memory until the service becomes unavailable.
Summary
What happened
Improper input validation in wolfSSL 3.12.0 through 5.8.3 allows remote attackers to exhaust server resources with a TLS 1.3 ClientHello. The KeyShareEntry parser accepts repeated entries for the same supported group and allocates new key-share state without releasing the prior allocation. Only server-side TLS 1.3 processing is exposed; repeated unauthenticated handshakes consume CPU and memory until the service becomes unavailable.
The record
- CVE
- CVE-2025-11936
- Published
- Nov 21, 2025
- Updated
- Dec 8, 2025
- Vendor
- wolfSSL
- Product
- wolfSSL
- Classifications
- CWE-20, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 21, 2025CVE publishedPublication date reported by the CVE source.
- Dec 8, 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=3.12.0 <5.8.4
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.
Weakness, pattern, technique
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