How severe is GHSA-2gqq-gqf2-x968?

GHSA-2gqq-gqf2-x968 has a CVSS score of 3.7/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-2gqq-gqf2-x968?

GHSA-2gqq-gqf2-x968 affects the following packages: undici (npm), undici (npm). Ecosystems affected: npm.

How do I fix GHSA-2gqq-gqf2-x968?

Update undici to 7.29.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2gqq-gqf2-x968 is resolved across your whole dependency graph.

How do I detect GHSA-2gqq-gqf2-x968 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for undici, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-2gqq-gqf2-x968 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-2gqq-gqf2-x968 actively exploited in the wild?

No public exploit code has been indexed for GHSA-2gqq-gqf2-x968 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-2gqq-gqf2-x968?

GHSA-2gqq-gqf2-x968 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 9th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-2gqq-gqf2-x968?

GHSA-2gqq-gqf2-x968 is classified as Improper Input Validation (CWE-20), CWE-248 (CWE-248). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-2gqq-gqf2-x968 published, and has it been updated?

GHSA-2gqq-gqf2-x968 was published on September 29, 2026 and was last updated on September 29, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

LOW severity

undici vulnerable to response truncation via oversized chunked responses in the dump interceptorGHSA-2gqq-gqf2-x968

LOWFix: nodejs/undici@21693f4

GHSA-2gqq-gqf2-x968 is a low-severity (CVSS 3.7) Improper Input Validation vulnerability in undici. A fix is available for undici — see the affected versions and patch details below.

Also known asCVE-2026-84947

Published

Sep 29, 2026

Updated

Sep 29, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-2gqq-gqf2-x968.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs9th percentile — riskier than 9% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-2gqq-gqf2-x968 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 395,249 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

9Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

undicinpm

143.8Mdownloads / week

Description

Impact

undici's interceptors.dump() reads and discards response bodies up to a configurable maxSize. When a response declares a Content-Length that exceeds maxSize, the request is aborted cleanly. When a response is sent chunked (no Content-Length) and its body exceeds maxSize, it is not aborted: the interceptor ends the response early once the accumulated size reaches maxSize, and continued delivery from the parser triggers an internal assertion that is caught and turned into a request abort and connection tear-down. The application observes a misleading 200 with an empty or truncated body while the connection is disconnected. Any application using the dump interceptor against untrusted or misbehaving upstreams is affected.

Patches

Upgrade to 7.29.1 or 8.10.2. The dump interceptor now enforces maxSize on both the declared and the received body size, aborting the request with a RequestAbortedError instead of returning a truncated response.

Workarounds

None. Avoid using interceptors.dump() with untrusted upstreams until upgraded.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`undici`	≥ 7.1.0&&< 7.29.1	7.29.1`npm install undici@7.29.1`
📦npm	`undici`	≥ 8.0.0&&< 8.10.2	8.10.2`npm install undici@8.10.2`

Affected Products

1 product · 2 configurations

Application

undicinodejs

≥ 8.0.0 && < 8.10.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for undici, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update undici to 7.29.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2gqq-gqf2-x968 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Moderate impact: A flaw in the undici library's dump interceptor can cause applications to terminate connections and receive truncated data when processing oversized chunked HTTP responses without a Content-Length header. This can lead to application instability and incomplete data handling in Red Hat products that…

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Source: Red Hat security advisory for GHSA-2gqq-gqf2-x968 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Hardened Images	`nodejs26-main-11.19.0-1.26.7.0.1.5.2.hum1`	RHSA-2026:54389
Red Hat Hardened Images	`nodejs24-main-11.16.0-1.24.18.1.0.2.2.hum1`	RHSA-2026:54438
Red Hat Hardened Images	`grafana12-4-main-12.4.10-0.2.hum1`	RHSA-2026:66008

Frequently Asked Questions

### Impact undici's `interceptors.dump()` reads and discards response bodies up to a configurable `maxSize`. When a response declares a `Content-Length` that exceeds `maxSize`, the request is aborted cleanly. When a response is sent chunked (no `Content-Length`) and its body exceeds `maxSize`, it is not aborted: the interceptor ends the response early once the accumulated size reaches `maxSize`, and continued delivery from the parser triggers an internal assertion that is caught and turned into a request abort and connection tear-down. The application observes a misleading `200` with an empty