Stateless, but not forgetful: How LLMs can whisper to their future selves

Based on the research paper: “Stateless Yet Not Forgetful: Implicit Memory as a Hidden Channel in LLMs” published at the4th IEEE Conference on Secure and Trustworthy Machine Learning SaTML, 2026...

Excessive Memory Use Buffering DTLS Records for a Future Epoch

...

openssl: excessive memory use buffering DTLS records for a future epoch

A flaw was found in OpenSSL. Receiving a DTLS Datagram Transport Layer Security record for a future epoch while a handshake is in progress causes OpenSSL to buffer an excessive amount of memory. This allows a peer to cause memory exhaustion, eventually resulting in a denial of service, using a...

openssl: excessive memory use buffering DTLS records for a future epoch

A flaw was found in OpenSSL. Receiving a DTLS Datagram Transport Layer Security record for a future epoch while a handshake is in progress causes OpenSSL to buffer an excessive amount of memory. This allows a peer to cause memory exhaustion, eventually resulting in a denial of service, using a...

CVE-2026-54874

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...

AZL-97953 CVE-2026-54874 affecting package openssl for versions less than 3.3.7-6

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...

AZL-97668 CVE-2026-54874 affecting package openssl-fips-provider 3.1.2-2

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...

ALPINE-CVE-2026-54874

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...

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

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...

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

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...

CVE-2026-54874

OpenSSL is vulnerable to a remote memory exhaustion Denial of Service risk in its DTLS component (CWE-405). While a handshake is in progress, a peer may move to a future epoch before the local endpoint catches up, causing OpenSSL to buffer early records. Instead of buffering only the necessary by...

CVE-2026-54874

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...

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

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...

CVE-2026-54874

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...

PT-2026-81301

Name of the Vulnerable Software and Affected Versions OpenSSL versions 1.0.2 through 4.0 Description Receiving a DTLS record for a future epoch during a handshake causes the system to buffer significantly more memory than the record requires. This occurs because the software retains the entire re...

CVE-2026-54874

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...

UBUNTU-CVE-2026-54874

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...

OpenSSL 1.1.1 < 1.1.1zi Multiple Vulnerabilities

The version of OpenSSL installed on the remote host is prior to 1.1.1zi. It is, therefore, affected by multiple vulnerabilities as referenced in the 1.1.1zi advisory. - Issue summary: Receiving a DTLS record for a future epoch while a handshake is in progress causes OpenSSL to buffer far more...

Excessive Memory Use Buffering DTLS Records for a Future Epoch

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...

JLSEC-2026-1351 Wasmtime is vulnerable to panic when dropping a `[Typed]Func::call_async` future

The affected versions of Wasmtime can panic if the host embedder drops the future returned by wasmtime::component::TypedFunc::callasync before it resolves. Details Starting with Wasmtime 39.0.0, the component-model-async feature became the default, which brought with it a new implementation of...