Skip to main content
Menu
CVEs

CVE

OpenSSL denial of service in DTLS handshake reassembly

CVE-2026-95690EUVD-2026-128605GHSA-G3CX-P9RC-JF32Published Updated Summary written by a model

5.3MediumCISA-ADP
Exploited
No known exploitation
Fix
Fixed in 4.1.1, 4.0.4, 3.5.10, 3.0.24, 1.1.1zk, and 1 more
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 4.1.1, 4.0.4, 3.5.10, 3.0.24, 1.1.1zk, or one of 1 more.

Summary

Receiving crafted out-of-sequence DTLS handshake fragments can make OpenSSL allocate a full message-length reassembly buffer for each buffered message. As a result, a small amount of data sent over the network can consume a large amount of memory.

Original description

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.

cve.now Index

45Pcve.now Index 45 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach20/20Affects OpenSSL (software on nearly every server, desktop or phone)
  • Severity5.3/10CVSS 5.3
  • No patch0/5No signal

What would change the score

  • Would score about 90 if added to CISA KEV
  • Would score about 85 if CISA's SSVC rates exploitation active
  • Would score about 50 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 4.1.1, 4.0.4, 3.5.10, 3.0.24, 1.1.1zk, or one of 1 more.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-95690 (Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-95690 (entry last updated 2026-11-18):
Affected:
- OpenSSL OpenSSL: from 4.1.0, fixed in 4.1.1; from 4.0.0, fixed in 4.0.4; from 3.5.0, fixed in 3.5.10; from 3.0.0, fixed in 3.0.24; from 1.1.1, fixed in 1.1.1zk; from 1.0.2, fixed in 1.0.2zt
Fixed versions: 4.1.1, 4.0.4, 3.5.10, 3.0.24, 1.1.1zk, 1.0.2zt.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-95690 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-95690 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/openssl/openssl/pull/33620
- https://github.com/openssl/openssl/pull/33729
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-95690
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-95690"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Affected versions

  • OpenSSL OpenSSL

    From 4.1.0 · fixed in 4.1.1; From 4.0.0 · fixed in 4.0.4; From 3.5.0 · fixed in 3.5.10; From 3.0.0 · fixed in 3.0.24; From 1.1.1 · fixed in 1.1.1zk; From 1.0.2 · fixed in 1.0.2zt

Evidence 4

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-95690
RecordNVD · CVE-2026-95690
Other links 2
PatchGitHub · openssl/openssl · Pull request #33620
PatchGitHub · openssl/openssl · Pull request #33729

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-95690

Is CVE-2026-95690 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-95690?

OpenSSL: from 4.1.0 before 4.1.1; from 4.0.0 before 4.0.4; from 3.5.0 before 3.5.10; from 3.0.0 before 3.0.24; from 1.1.1 before 1.1.1zk; from 1.0.2 before 1.0.2zt.Source: cve.now feed data

How do I fix CVE-2026-95690?

Upgrade to a fixed version: 4.1.1, 4.0.4, 3.5.10, 3.0.24, 1.1.1zk, or one of 1 more.Source: cve.now feed data

More CVEs