Skip to main content
Mallory
HighVulnerability

CVE-2026-54874: OpenSSL DTLS Future-Epoch Record Memory Amplification

Published Aug 25, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days20 mentions · peak 7 in a dayToday
CVSS7.5High · v3.1
EPSS0.62%50th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
OpenSSL Software Foundation
IdentifiersCVE-2026-54874CWE-405 · Asymmetric Resource Consumption…

CVE-2026-54874 is an asymmetric resource-consumption vulnerability in OpenSSL DTLS handshake processing. When a record claiming to belong to the next epoch arrives during an ongoing handshake, OpenSSL buffers it to accommodate legitimate packet reordering. The vulnerable implementation retains the entire approximately 16 KB receive buffer instead of only the record data. Up to 100 records can be buffered per association, allowing small forged records to retain approximately 1.7 MB of memory with roughly 1,200-fold network-to-memory amplification. Affected release branches include OpenSSL 4.0, 3.6, 3.5, 3.4, 3.0, 1.1.1, and 1.0.2 before their respective fixes. The vulnerable code is outside the OpenSSL FIPS module boundary.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A remote unauthenticated peer can cause disproportionate memory retention and potentially exhaust memory, resulting in denial of service against DTLS endpoints. The effect can be multiplied across concurrent associations. Confidentiality and integrity are not affected. OpenSSL assesses the issue as Low severity because memory retention is bounded per association and application-enforced association limits bound aggregate exposure.

Mitigation

If you can’t patch tonight, do this now.

Until patched, enforce conservative limits on concurrent DTLS associations to bound aggregate memory exposure. Restrict DTLS listeners to trusted networks or peers where feasible, and apply rate limiting and association-admission controls to reduce attackers' ability to create many associations. Monitor for abnormal memory growth and unusually large numbers of incomplete DTLS handshakes.

Remediation

Patch, then assume compromise.

Upgrade to OpenSSL 4.0.2, 3.6.4, 3.5.8, 3.4.7, or 3.0.22, according to the installed branch. Premium-support customers using legacy branches should upgrade to OpenSSL 1.1.1zi or 1.0.2zr. Distribution-managed and bundled installations should receive the applicable vendor security update, which may backport the fix without adopting the upstream version number. Restart or redeploy dependent services after updating so they load the patched library.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
OpenSSL Software FoundationOpensslapplication
FAQ

Frequently asked questions

Is CVE-2026-54874 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-54874 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-54874?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-54874.
Is there a patch for CVE-2026-54874?
Upgrade to OpenSSL 4.0.2, 3.6.4, 3.5.8, 3.4.7, or 3.0.22, according to the installed branch. Premium-support customers using legacy branches should upgrade to OpenSSL 1.1.1zi or 1.0.2zr.
What products are affected by CVE-2026-54874?
OpenSSL Software Foundation Openssl.
How severe is CVE-2026-54874?
CVE-2026-54874 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.62% (50th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

82 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
tenable nessus pluginsNews · Nov 16, 2026EulerOS Virtualization 2.10.0 : openssl (EulerOS-SA-2026-5044) | Tenable®An OpenSSL vulnerability covered by advisory EulerOS-SA-2026-5044 for EulerOS Virtualization 2.10.0. The content provides no vulnerability-specific technical details.Read more ↗tenable nessus pluginsNews · Nov 16, 2026EulerOS Virtualization 2.12.1 : openssl (EulerOS-SA-2026-4890) | Tenable®A vulnerability referenced by the OpenSSL security update EulerOS-SA-2026-4890 for EulerOS Virtualization 2.12.1. The supplied CVSS vectors indicate a network-accessible, low-complexity attack requiring no privileges or user interaction, with high availability impact and no confidentiality or integrity impact.Read more ↗tenable nessus pluginsNews · Nov 16, 2026EulerOS Virtualization 2.12.0 : openssl (EulerOS-SA-2026-4951) | Tenable®A vulnerability listed in the OpenSSL security advisory EulerOS-SA-2026-4951 for EulerOS Virtualization 2.12.0. Its associated CVSS vector indicates a remotely reachable availability impact requiring neither privileges nor user interaction. The excerpt provides no underlying technical cause. Patches were published on November 13, 2026.Read more ↗tenable nessus pluginsNews · Nov 16, 2026EulerOS Virtualization 2.10.1 : openssl (EulerOS-SA-2026-5004) | Tenable®Listed in OpenSSL security advisory EulerOS-SA-2026-5004 for EulerOS Virtualization 2.10.1. The content provides no vulnerability-specific technical description. A patch publication date of November 17, 2026 is listed.Read more ↗
+45 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity11Community discussion across Reddit, Mastodon, and other social sources.