VulnerabilityPublished 29 Sep 2026Updated 17 Oct 2026

CVE-2026-75804: Issue summary · OpenSSL QUIC stack does not enforce connection level flow control for streams

Affects nodejsSource GCVE Database

Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 3.5.5-1ubuntu3.6 when convenient.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.5.5-1ubuntu3.6

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-gjmh-wx93-r4pw

What to do

Upgrade the Ubuntu openssl package to 3.5.5-1ubuntu3.6.

Affected software

Product	Affected	Fixed in
Ubuntu 26.10edk2`pkg:deb/ubuntu/edk2?arch=source&distro=stonking`Other threats	Affected 2025.11-3ubuntu7 – 2026.05-2ubuntu3 5 affected builds	Fixed in–
Ubuntu 26.10edk2-hwe`pkg:deb/ubuntu/edk2-hwe?arch=source&distro=stonking`Other threats	Affected 2025.11-3ubuntu8 – 2026.05-2ubuntu3 5 affected builds	Fixed in–
Ubuntu 26.04 LTSedk2`pkg:deb/ubuntu/edk2?arch=source&distro=resolute`Other threats	Affected 2025.02-8ubuntu3 – 2025.11-3ubuntu7.3 5 affected builds	Fixed in–
Ubuntu 26.04 LTSedk2-hwe`pkg:deb/ubuntu/edk2-hwe?arch=source&distro=resolute`Other threats	Affected =2025.11-3ubuntu6 =2025.11-3ubuntu8 =2025.11-3ubuntu8.2	Fixed in–
Ubuntu 26.04 LTSopenssl`pkg:deb/ubuntu/openssl?arch=source&distro=resolute`Other threats	Affected <3.5.5-1ubuntu3.6	Fixed in 3.5.5-1ubuntu3.6
Ubuntu Pro 22.04 LTSnodejs`pkg:deb/ubuntu/nodejs?arch=source&distro=esm-apps/jammy`Other threats	Affected 12.22.5~dfsg-5ubuntu1 – 12.22.9~dfsg-1ubuntu3.6+esm2 12 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available for this vulnerability. Users should apply the official updates to the affected Node.js versions to remediate the issue. No additional mitigation steps are indicated by the vendor advisory.

Description

A vulnerability in the OpenSSL QUIC stack used by Node.js allows a remote peer to bypass connection-level flow control for streams. This can lead to excessive memory allocation on the local system, potentially up to 100MB per connection instead of the intended 768 KiB. Exploitation requires specific conditions involving multiple streams and data patterns. The OpenSSL FIPS module is not affected as the QUIC implementation lies outside its boundary. The issue has a CVSS score of 5.3 (low severity) and affects multiple specific Node.js versions. A patch is available to address this vulnerability.

CWE-770Allocation of Resources Without Limits or Throttling (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #25
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.
Requirements
Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
Architecture and Design
Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.4 (opens in a new tab)
V13.4.1 (opens in a new tab)
V11.1.4 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Exponential Data Expansion (opens in a new tab)
Serialized Data Parameter Blowup (opens in a new tab)
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 18 Oct 2026, 02:44 UTC

WeaknessesCWE-770

Technical details

References

Community reviews

Related threats