CVE-2026-54874: OpenSSL DTLS Future-Epoch Record Memory Amplification
- Vendor
- OpenSSL Software Foundation
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.
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.
Exploits
No public exploits tracked yet. Mallory keeps watching.
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.
References
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.
Recent activity
78 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.