How severe is GHSA-m4v8-wqvr-p9f7?

GHSA-m4v8-wqvr-p9f7 has a CVSS score of 3.9/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-m4v8-wqvr-p9f7?

GHSA-m4v8-wqvr-p9f7 affects the following packages: undici (npm), undici (npm). Ecosystems affected: npm.

How do I fix GHSA-m4v8-wqvr-p9f7?

Update undici to 5.28.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m4v8-wqvr-p9f7 is resolved across your whole dependency graph.

How do I detect GHSA-m4v8-wqvr-p9f7 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-m4v8-wqvr-p9f7 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-m4v8-wqvr-p9f7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-m4v8-wqvr-p9f7 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-m4v8-wqvr-p9f7?

GHSA-m4v8-wqvr-p9f7 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 55th 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-m4v8-wqvr-p9f7?

GHSA-m4v8-wqvr-p9f7 is classified as CWE-285 (CWE-285), CWE-863 (CWE-863). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-m4v8-wqvr-p9f7 published, and has it been updated?

GHSA-m4v8-wqvr-p9f7 was published on April 4, 2024 and was last updated on November 4, 2025. 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's Proxy-Authorization header not cleared on cross-origin redirect for dispatch, request, stream, pipelineGHSA-m4v8-wqvr-p9f7

LOWFix: nodejs/undici@64e3402

GHSA-m4v8-wqvr-p9f7 is a low-severity (CVSS 3.9) CWE-285 vulnerability in undici. A fix is available for undici — see the affected versions and patch details below.

Also known asCVE-2024-30260

Published

Apr 4, 2024

Updated

Nov 4, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 5, 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-m4v8-wqvr-p9f7.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

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

318.2Mdownloads / week

Description

Impact

Undici cleared Authorization and Proxy-Authorization headers for fetch(), but did not clear them for undici.request().

Patches

This has been patched in https://github.com/nodejs/undici/commit/6805746680d27a5369d7fb67bc05f95a28247d75. Fixes has been released in v5.28.4 and v6.11.1.

Workarounds

use fetch() or disable maxRedirections.

References

Linzi Shang reported this.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`undici`	all versions	5.28.4`npm install undici@5.28.4`
📦npm	`undici`	≥ 6.0.0&&< 6.11.1	6.11.1`npm install undici@6.11.1`

Affected Products

2 products · 5 configurations

fedorafedoraproject

3 versions

383940

Application

undicinodejs

≥ 6.0.0 && < 6.11.1

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 5.28.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m4v8-wqvr-p9f7 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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 HatLow

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options don't 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-m4v8-wqvr-p9f7 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat OpenShift Dev Spaces 3 Containers	`devspaces/dashboard-rhel8:3.16-27`	RHSA-2024:6667

Frequently Asked Questions

### Impact Undici cleared Authorization and Proxy-Authorization headers for `fetch()`, but did not clear them for `undici.request()`. ### Patches This has been patched in https://github.com/nodejs/undici/commit/6805746680d27a5369d7fb67bc05f95a28247d75. Fixes has been released in v5.28.4 and v6.11.1. ### Workarounds use `fetch()` or disable `maxRedirections`. ### References Linzi Shang reported this. * https://hackerone.com/reports/2408074 * https://github.com/nodejs/undici/security/advisories/GHSA-3787-6prv-h9w3

O3 Security · Impact-Aware SCA

Is GHSA-m4v8-wqvr-p9f7 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works