Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

CVE-2026-54874— Excessive Memory Use Buffering DTLS Records for a Future Epoch

Quick assessment

Affected
OpenSSL OpenSSL
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

以下是对该漏洞描述信息的中文翻译： --- 问题摘要： 在握手进行中接收属于未来时态（epoch）的 DTLS 记录，会导致 OpenSSL 缓存远大于该记录本身所需的内存。 影响摘要： 对端可以通过发送少量网络流量，使 OpenSSL DTLS 终端保留不成比例的大量内存，从而导致拒绝服务（DoS）。 CWE： CWE-405：不对称资源消耗（放大效应） 详细描述： 在 DTLS 握手过程中，对端可能已经合法地进入了下一个时态（例如，在本地终端处理完相同转换之前，它已发送了 ChangeCipherSpec 和

AI Predicted 5.3 Difficulty: Easy

Affected Version Matrix 7

VendorProduct Version RangeStatus
OpenSSL OpenSSL 4.0.0< 4.0.2 affected
3.6.0< 3.6.4 affected
3.5.0< 3.5.8 affected
3.4.0< 3.4.7 affected
3.0.0< 3.0.22 affected
1.1.1< 1.1.1zi affected
1.0.2< 1.0.2zr affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-54874

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Excessive Memory Use Buffering DTLS Records for a Future Epoch
Source: CVE Program / CVE List V5
Vulnerability Description
Issue summary: Receiving a DTLS record for a future epoch while a handshake is in progress causes OpenSSL to buffer far more memory than the record itself requires. Impact summary: A peer can use a small amount of network traffic to make an OpenSSL DTLS endpoint retain a disproportionately large amount of memory, which may lead to a Denial of Service. CWE: CWE-405: Asymmetric Resource Consumption (Amplification) Description: While a DTLS handshake is in progress, a peer may legitimately have already moved on to the next epoch (for example, having sent its ChangeCipherSpec and Finished messages) before the local endpoint has processed the same transition, typically because of reordering on the underlying UDP transport. OpenSSL buffers such early records so that they can be processed once the local endpoint catches up. Buffering a record currently retains the entire read buffer it arrived in, which is sized to hold the largest possible DTLS record (around 16 kilobytes), rather than just the bytes that make up the record itself. Up to 100 such records may be buffered per connection. As a result, a peer that sends a stream of small forged records claiming to belong to the next epoch can cause an OpenSSL DTLS endpoint to retain around 1.7 megabytes of memory, despite sending only a small fraction of that amount of data over the network. An attacker therefore gains a memory amplification factor of around 1200, and can multiply the effect across as many associations as it is able to open, making this a remote memory exhaustion Denial of Service risk for DTLS servers. Since the memory retained per connection remains bounded, and any limit an application already places on the number of concurrent associations also bounds the total exposure, this issue has been assessed as Low severity. FIPS impact: no No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary. OpenSSL 4.0, 3.6, 3.5, 3.4, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.2. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.4. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.8. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.7. OpenSSL 3.0 users should upgrade to OpenSSL 3.0.22. Premium support customers only: OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1zi OpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zr This issue was reported on 18 May 2026 by Amazon Web Services. The fix has been developed by Matt Caswell. -- cut (non-publishing metadata for internal use) -- Reported by: Amazon Web Services Fixed by: Matt Caswell
Source: CVE Program / CVE List V5
CVSS Information
N/A
Source: CVE Program / CVE List V5
Vulnerability Type
不对称的资源消耗(放大攻击)
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
OpenSSL OpenSSL 4.0.0 ~ 4.0.2 -

II. Public POCs for CVE-2026-54874

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-54874

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-54874 (5)

Vendor Advisories for CVE-2026-54874 (1)

Same Patch Batch · OpenSSL · 2026-08-25 · 9 CVEs total

CVE-2026-75803 AEAD Forgeries with Empty Ciphertext When Using EVP_Cipher()
CVE-2026-18798 QUIC Server May Trigger Double Free When Processing INITIAL Packet
CVE-2026-63074 CMP Indefinite Cache Growth of ExtraCerts
CVE-2026-63072 Heap Buffer Overflow in CMS Key Unwrapping
CVE-2026-63073 Untrusted Sender DN Used as Format String in CMP Response Validation
CVE-2026-63075 QUIC ACK-only Packet Retention Can Cause Memory Exhaustion
CVE-2026-63076 Invalid Pointer Dereference in CMP Server via Crafted protectionAlg
CVE-2026-14457 RPK Server Signature Algorithm Selection Can Dereference a Missing Certificate

IV. Related Vulnerabilities

Same product: OpenSSL
Same vendor: OpenSSL
Same weakness: CWE-405

V. Comments for CVE-2026-54874

No comments yet

Leave a comment