Skip to main content
Mallory
HighVulnerability

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

Published Aug 25, 2026 · Updated 4 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days16 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 record buffering. During an active handshake, OpenSSL buffers records belonging to the next epoch to accommodate legitimate handshake transitions and UDP packet reordering. The vulnerable implementation retains the entire receive buffer, approximately 16 KB, for each buffered record rather than retaining only the record's bytes. A peer can therefore send small forged next-epoch records to trigger disproportionate memory retention. Up to 100 records can be buffered per association, consuming approximately 1.7 MB and producing 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. The affected 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 increase memory consumption on an affected DTLS endpoint and potentially exhaust server memory by repeating the attack across multiple concurrent associations, causing denial of service. Memory retention is bounded to approximately 1.7 MB per association, so application limits on concurrent associations constrain aggregate exposure. OpenSSL assesses the issue as Low severity for this reason. No confidentiality or integrity impact is identified, and OpenSSL FIPS modules themselves are not affected.

Mitigation

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

Until patched, enforce conservative limits on concurrent DTLS associations, including incomplete handshakes, to bound aggregate memory retention. Restrict DTLS listeners to trusted peers or networks where feasible, and apply rate limiting and admission controls to reduce association creation by untrusted peers. Monitor DTLS-serving processes for abnormal memory growth and unusually large numbers of incomplete handshakes. These controls reduce exposure but do not correct the buffering defect.

Remediation

Patch, then assume compromise.

Upgrade to the fixed release for the deployed OpenSSL branch: 4.0.2, 3.6.4, 3.5.8, 3.4.7, or 3.0.22. Premium-support customers using legacy branches should upgrade to 1.1.1zi or 1.0.2zr. For distribution-managed installations and products bundling OpenSSL, apply the corresponding vendor security update, which may backport the fix without adopting the upstream version number. Update affected container images and bundled dependencies, then restart or redeploy dependent services to 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 12, 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 12, 2026, Mallory has found no public exploit for CVE-2026-54874.
Is there a patch for CVE-2026-54874?
Upgrade to the fixed release for the deployed OpenSSL branch: 4.0.2, 3.6.4, 3.5.8, 3.4.7, or 3.0.22. Premium-support customers using legacy branches should upgrade to 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 12, 2026.
Activity feed

Recent activity

78 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 12, 2026SUSE SLES15: libopenssl-1_0_0-devel / libopenssl10 / libopenss... | Tenable®Excessive memory use when buffering DTLS records for a future epoch in OpenSSL packages supplied for SUSE SLES15 and SLES_SAP15. Advisory SUSE-SU-2026:5209-1 provides security updates. Nessus relies on installed package version information rather than direct vulnerability testing.Read more ↗tenable nessus pluginsNews · Nov 6, 2026EulerOS 2.0 SP12 : openssl (EulerOS-SA-2026-4508) | Tenable®An OpenSSL DTLS memory-amplification vulnerability can cause remote denial of service. During a handshake, small forged future-epoch records retain entire approximately 16 KB read buffers, with up to 100 records buffered per connection. This allows approximately 1.7 MB of retained memory per association and an amplification factor around 1200. The advisory assesses the issue as Low severity because per-connection consumption is bounded, although the Nessus plugin reports High severity. Affected branches are OpenSSL 4.0, 3.6, 3.5, 3.4, 3.0, 1.1.1, and 1.0.2. Fixed releases are 4.0.2, 3.6.4, 3.5.8, 3.4.7, 3.0.22, and, for premium support customers, 1.1.1zi and 1.0.2zr. Limiting concurrent DTLS associations bounds total exposure. FIPS modules are unaffected. Nessus identifies affected packages using self-reported versions rather than testing exploitation.Read more ↗tenable nessus pluginsNews · Nov 6, 2026EulerOS 2.0 SP12 : openssl (EulerOS-SA-2026-4431) | Tenable®An OpenSSL DTLS memory-amplification vulnerability allows a remote peer to cause disproportionate memory retention using small forged records during a handshake. Up to approximately 1.7 MB can be retained per connection, with an amplification factor around 1200. Opening multiple associations can cause memory exhaustion and denial of service. The advisory assesses the issue as Low severity because memory retention per connection is bounded, although the Nessus plugin reports a High severity rating. Nessus identifies affected installations through self-reported package versions rather than exploitation testing.Read more ↗tenable nessus pluginsNews · Nov 2, 2026Photon OS 4.0: Openssl PHSA-2026-4.0-1077 | Tenable®A vulnerability affecting the OpenSSL package on Photon OS 4.0, addressed by an available security update. The content does not describe its specific mechanism or impact.Read more ↗
+41 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.