Bookmarks

    Nothing saved yet. Use the bookmark on any article. Bookmarks are kept on this device only: they stay private and work without an account.

    Settings

    Appearance

    Reading mode

    Font size

    Content width

    Line spacing

    Keyboard shortcuts

    /
    Search
    j k
    Next / previous story
    ← →
    Previous / next section (columns)
    b
    Bookmarks
    s
    Settings
    r
    Columns / scroll
    t
    Light / dark

    Saved in this browser only.

    Ping2Prompt
    Subscribe to the Weekly Brief Sign in
    Ping2Prompt story card: OpenSSL QUIC servers can leak memory on rejected streams (CVE-2026-124709). Low, OpenSSL.
    Photo by Mikael Seegen / Unsplash

    OpenSSL QUIC servers can leak memory on rejected streams (CVE-2026-124709)

    OpenSSL

    A slow memory leak in OpenSSL's QUIC server

    CVE-2026-124709 is a memory leak in the OpenSSL QUIC server's stream handling, specifically the path that rejects streams under the incoming stream policy. A client that finishes the QUIC handshake can open and reset streams over and over, and the server's memory grows without limit until the process runs out and drops every connection on it. The advisory rates it Low, because growth is slow, the attacker needs a long-lived connection, and nothing is corrupted or disclosed. The advisory gives no severity score or vector, and the sources do not say whether the flaw is being exploited, so treat its exploitation status as unknown.

    Why a reset stream is never cleaned up

    When the policy rejects a peer-opened stream, OpenSSL queues a STOP_SENDING frame, marks the stream deleted and gives the peer its stream credit back. A deleted stream is freed only after its receive side is fully drained, which means the peer has acknowledged STOP_SENDING. If the peer sends RESET_STREAM first, that cancels the pending STOP_SENDING.

    It is never sent or acknowledged, so the stream stays in memory for the life of the connection. Each retained stream costs about 300 bytes, and the peer's stream credit window sets how fast they pile up.

    Default QUIC servers reach the vulnerable path

    You do not need an unusual setup. Once a connection has a default stream, meaning the application has read from or written to it, the default policy rejects any other streams the application does not accept. The tutorial server behaves this way.

    Applications that set the REJECT policy explicitly are affected too. The attacker must complete a handshake and keep the connection open, so this is a remote attack by a connected client. The affected code sits outside the FIPS module boundary, so FIPS is not affected.

    Check the advisory for a fixed OpenSSL version

    The record does not give affected version ranges or a fixed version, so the table below is empty. Read the OpenSSL advisory at https://openssl-library.org/news/secadv/20261117.txt to find the release that carries the fix. The NVD record links three OpenSSL commits: 22291a6af12f158fbb13bfbd572a33dbdbf290d2, ead311df1037e7994a6d86c7e862d71ad59c52c7 and f3acb0a3328046741479482c51cec815839e1b05.

    If you run a QUIC server built on OpenSSL, update once a fixed release is confirmed. No workaround is listed in the record. Until you can update, watch the server's memory use on long-lived QUIC connections.

    Sources


    This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our editorial methodology and the corrections log. Spotted an error? Email [email protected].

    Continue

    Share on Bluesky · Mastodon · Email ·

    Discussion