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
Published: 2026-08-25
Score: 7.5 High
EPSS: < 1% Very Low
KEV: No
Impact: Remote Memory Exhaustion Denial of Service
Action: Immediate Patch
AI Analysis

Impact

The vulnerability, identified as CWE‑405 (Asymmetric Resource Consumption), occurs when a DTLS handshake is in progress and a peer sends a record for a future epoch. OpenSSL buffers the entire read buffer, which can be up to 16 KB, and may buffer up to 100 such records per connection, consuming around 1.7 MB of memory per association even though only a small amount of data is transmitted. This memory amplification can cause a denial of service by exhausting available memory on a DTLS server while maintaining an otherwise normal connection.

Affected Systems

Vulnerable OpenSSL releases include 4.0, 3.6, 3.5, 3.4, 3.0, 1.1.1, and 1.0.2. Users should upgrade to OpenSSL 4.0.2, 3.6.4, 3.5.8, 3.4.7, or 3.0.22. Premium support customers should install OpenSSL 1.1.1zi or 1.0.2zr.

Risk and Exploitability

The CVSS assessment lists a score of 7.5, but the CVE description categorizes the vulnerability as low severity. The EPSS score is not available and the issue is not listed in CISA KEV, indicating a relatively low likelihood of exploitation in the current landscape. Based on the description, it is inferred that the attack vector is a network-based exploitation via UDP, requiring an attacker to send forged DTLS records belonging to a future epoch to a reachable DTLS endpoint. The exploitation complexity is moderate, but the attack has a low network footprint; an attacker can send a short burst of crafted packets to induce memory buffering that may exhaust available memory if a large number of concurrent DTLS associations are processed.

Generated by OpenCVE AI on August 25, 2026 at 17:07 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the OpenSSL library to the fixed release: 4.0.2, 3.6.4, 3.5.8, 3.4.7, or 3.0.22, according to the current version in use.
  • For customers with premium support, install the specific updates 1.1.1zi or 1.0.2zr as recommended.
  • Enforce a limit on the number of concurrent DTLS associations or apply firewall ingress rules to throttle connections, thereby reducing the overall memory bound and mitigating the impact if an upgrade is delayed.

Generated by OpenCVE AI on August 25, 2026 at 17:07 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DSA Debian DSA DSA-6465-1 openssl security update
Ubuntu USN Ubuntu USN USN-8678-1 OpenSSL vulnerabilities
History

Fri, 11 Sep 2026 23:45:00 +0000

Type Values Removed Values Added
CPEs cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:*

Wed, 26 Aug 2026 00:15:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

threat_severity

Low


Tue, 25 Aug 2026 15:30:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Tue, 25 Aug 2026 15:00:00 +0000

Type Values Removed Values Added
First Time appeared Openssl
Openssl openssl
Vendors & Products Openssl
Openssl openssl

Tue, 25 Aug 2026 13:15:00 +0000

Type Values Removed Values Added
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
Title Excessive Memory Use Buffering DTLS Records for a Future Epoch
Weaknesses CWE-405
References

cve-icon MITRE

Status: PUBLISHED

Assigner: openssl

Published:

Updated: 2026-08-25T14:28:37.339Z

Reserved: 2026-06-16T10:18:08.635Z

Link: CVE-2026-54874

cve-icon Vulnrichment

Updated: 2026-08-25T14:28:29.699Z

cve-icon NVD

Status : Analyzed

Published: 2026-08-25T13:19:24.033

Modified: 2026-09-11T21:16:28.067

Link: CVE-2026-54874

cve-icon Redhat

Severity : Low

Publid Date: 2026-08-25T00:00:00Z

Links: CVE-2026-54874 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-25T17:15:05Z

Weaknesses
  • CWE-405

    Asymmetric Resource Consumption (Amplification)