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 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.
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.
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 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.
Recent activity
82 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.