MediumCVE-2026-75804

    QUIC Connection-Level Flow Control is Not Enforced for Streams (CVE-2026-75804)

    Published Last modified Sources: Red Hat, SUSE, Ubuntu, Debian, BSI, CVE.org, EUVD, Msrc Update Guide

    Share

    What is affected, what to do

    A flaw was found in OpenSSL. A remote attacker can cause a Denial of Service (DoS) due to missing connection-level flow control enforcement in the QUIC protocol implementation.

    Update OpenSSL to version 4.0.3, OpenSSL to version 3.6.5, OpenSSL to version 3.5.9.

    Affected
    • OpenSSL lt 4.0.0..4.0.3
    • OpenSSL lt 3.6.0..3.6.5
    • OpenSSL lt 3.5.0..3.5.9
    • OpenSSL lt 3.4.0..3.4.8
    Fixed in
    • OpenSSL 4.0.3
    • OpenSSL 3.6.5
    • OpenSSL 3.5.9
    • OpenSSL 3.4.8

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    5.3

    XIEM Effective CVSS

    Highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    5.3

    CVSS v3

    Severity Medium on the scale from 0 to 10.

    Source: Red Hat, SUSE, Ubuntu, Debian, BSI, CVE.org, EUVD, Msrc Update Guide

    0.5 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 45.3

    Show all metrics
    Severity
    Medium
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    70.22 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    5.3 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    5.3
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.5 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    45.3
    High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: none known · automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 29 September 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-770

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    A flaw was found in OpenSSL. A remote attacker can cause a Denial of Service (DoS) due to missing connection-level flow control enforcement in the QUIC protocol implementation. By opening multiple streams that respect individual stream limits while preventing data consumption, the attacker can force the system to buffer far more data than permitted by the connection limit. This excessive memory allocation can exhaust available system resources and degrade or terminate the service.

    Source: redhat_csaf, suse_csaf, Ubuntu Security Notices, Debian Security Advisories, BSI WID Portal, BSI CSAF, NVD (NIST), cvelistv5, ENISA EUVD, Microsoft Security Update Guide

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    OpenSSLOpenSSL
    • 3.4.0 – < 3.4.8
    • 3.5.0 – < 3.5.9
    • 3.6.0 – < 3.6.5
    • 4.0.0 – < 4.0.3
    • 3.4.8
    • 3.5.9
    • 3.6.5
    • 4.0.3
    opensslopenssl
    • 4.0.0 – < 4.0.3
    • 3.5.0 – < 3.5.9
    • 3.6.0 – < 3.6.5
    • 3.4.0 – < 3.4.8
    • 4.0.3
    • 3.5.9
    • 3.6.5
    • 3.4.8

    Vendors and products

    Affected operating systems

    Affected operating systems
    Linuxdebianopenssltrixie

    Weakness classes (CWE)

    • CWE-770Allocation of Resources Without Limits or Throttling

      Base

      The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

      Entry at MITRE CWE-770

    References & sources

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Initial analysis by NVDNVD

      Show 6 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Product configurationadded
      —
      OR *cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* versions from (including) 3.4.0 up to (excluding) 3.4.8 *cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* versions from (including) 3.5.0 up to (excluding) 3.5.9 *cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* versions from (including) 3.6.0 up to (excluding) 3.6.5 *cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* versions from (including) 4.0.0 up to (excluding) 4.0.3
      Reference typeadded
      —
      OpenSSL Software Foundation: https://github.com/openssl/openssl/commit/2e8f54666b3fb7b05ff5f58aa6cac9285163654e Types: Patch
      Reference typeadded
      —
      OpenSSL Software Foundation: https://github.com/openssl/openssl/commit/4533ee8a5686c953ed3b644738ac4bdf20806538 Types: Patch
      Reference typeadded
      —
      OpenSSL Software Foundation: https://github.com/openssl/openssl/commit/64d3102fb5b54311e92517f26ba00169d719e74a Types: Patch
      Reference typeadded
      —
      OpenSSL Software Foundation: https://github.com/openssl/openssl/commit/f9eaecf5bdd6692da052bc65b0332af2a938ac03 Types: Patch
      Reference typeadded
      —
      OpenSSL Software Foundation: https://openssl-library.org/news/secadv/20260929.txt Types: Vendor Advisory

      Source identifier: nvd@nist.gov

    2. Record modifiedCISA ADP

      CVSS V3.1: AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

      CISA assessment (SSVC): exploitation: none known, automatable: yes

      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      CVSSadded
      —
      AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
      SSVC assessmentadded
      —
      {"id":"CVE-2026-75804","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-09-29T17:15:09.218928Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    3. Receivedopenssl.org

      Show 8 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      Issue summary: OpenSSL QUIC stack does not enforce connection level flow control for streams. Remote peers may send more bytes as long as they fit within the stream flow control limits. Impact summary: A malicious remote peer may exploit the lack of connection flow control for streams to make the QUIC stack receive ~100MB of memory instead of 768 KiB (default flow control window size). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The local QUIC stack advertises two flow control limits to its remote peer: stream flow control limit and connection flow control limit. The remote peer must follow both limits when transmitting stream data. Whenever the local QUIC stack receives a stream frame, it validates that the size of the received stream frame stays within flow control limits. If either limit is exceeded (stream level or connection level), then the QUIC stack must close the connection with a flow control error. The vulnerable OpenSSL QUIC stack enforces the stream-level but not the connection-level limit. To exploit the issue, three conditions must be met: - the remote peer opens several streams - each stream must stay within the stream-level flow control limit - there must be no zero-offset byte sent on any of the streams (to prevent the vulnerable QUIC stack from consuming data). By meeting the conditions above, the remote peer may make the local stack allocate 2 x MAX_STREAMS x (stream flow control limit) bytes of memory. MAX_STREAMS defaults to 100, and the limit applies to both bidirectional and unidirectional streams, making it 200 in total. The default flow control window for a stream is 512kB. The remote peer may force the vulnerable QUIC stack to allocate 100MB of heap per connection. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.
      Weakness type (CWE)added
      —
      CWE-770
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/75xxx/CVE-2026-75804.json">CVE-2026-75804</a>
      Referenceadded
      —
      https://github.com/openssl/openssl/commit/2e8f54666b3fb7b05ff5f58aa6cac9285163654e
      Referenceadded
      —
      https://github.com/openssl/openssl/commit/4533ee8a5686c953ed3b644738ac4bdf20806538
      Referenceadded
      —
      https://github.com/openssl/openssl/commit/64d3102fb5b54311e92517f26ba00169d719e74a
      Referenceadded
      —
      https://github.com/openssl/openssl/commit/f9eaecf5bdd6692da052bc65b0332af2a938ac03
      Referenceadded
      —
      https://openssl-library.org/news/secadv/20260929.txt

      Source identifier: openssl-security@openssl.org

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-75804
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-75804"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-75804.svg?lang=en" alt="CVE-2026-75804 – NEOSEC Intel" height="20"></a>