OpenSSL up to 3.0.23/3.5.9/4.0.3/4.1.0 DTLS Handshake allocation of resources
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.32+ |
Summary
A vulnerability classified as problematic has been found in OpenSSL up to 3.0.23/3.5.9/4.0.3/4.1.0. This impacts an unknown function of the component DTLS Handshake. Performing a manipulation results in allocation of resources. This vulnerability is known as CVE-2026-95690. Remote exploitation of the attack is possible. No exploit is available. It is recommended to upgrade the affected component.
Details
A vulnerability was found in OpenSSL up to 3.0.23/3.5.9/4.0.3/4.1.0. It has been classified as problematic. This affects some unknown processing of the component DTLS Handshake. The manipulation with an unknown input leads to a allocation of resources vulnerability. CWE is classifying the issue as CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. This is going to have an impact on availability. The summary by CVE is:
Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-95690 since 09/22/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 11/18/2026). MITRE ATT&CK project uses the attack technique T1499 for this issue.
Upgrading to version 1.0.2zt, 1.1.1zk, 3.0.24, 3.5.10, 4.0.4 or 4.1.1 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
- 3.0.0
- 3.0.1
- 3.0.2
- 3.0.3
- 3.0.4
- 3.0.5
- 3.0.6
- 3.0.7
- 3.0.8
- 3.0.9
- 3.0.10
- 3.0.11
- 3.0.12
- 3.0.13
- 3.0.14
- 3.0.15
- 3.0.16
- 3.0.17
- 3.0.18
- 3.0.19
- 3.0.20
- 3.0.21
- 3.0.22
- 3.0.23
- 3.5.0
- 3.5.1
- 3.5.2
- 3.5.3
- 3.5.4
- 3.5.5
- 3.5.6
- 3.5.7
- 3.5.8
- 3.5.9
- 4.0
- 4.0.0
- 4.0.1
- 4.0.2
- 4.0.3
- 4.1.0
License
Website
- Product: https://www.openssl.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Allocation of resourcesCWE: CWE-770 / CWE-400 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: OpenSSL 1.0.2zt/1.1.1zk/3.0.24/3.5.10/4.0.4/4.1.1
Timeline
09/22/2026 CVE reserved11/18/2026 Advisory disclosed
11/18/2026 VulDB entry created
11/18/2026 VulDB entry last update
Sources
Product: openssl.orgAdvisory: github.com
Status: Confirmed
CNA: openssl
CVE: CVE-2026-95690 (🔒)
GCVE (CVE): GCVE-0-2026-95690
GCVE (VulDB): GCVE-100-439305
Entry
Created: 11/18/2026 13:02Changes: 11/18/2026 13:02 (55)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.