How severe is CVE-2024-30261?

CVE-2024-30261 has a CVSS score of 2.6/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2024-30261?

CVE-2024-30261 affects the following packages: undici (npm), undici (npm). Ecosystems affected: npm.

How do I fix CVE-2024-30261?

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

How do I detect CVE-2024-30261 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 CVE-2024-30261 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 CVE-2024-30261 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2024-30261, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2024-30261?

CVE-2024-30261 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 57th 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 CVE-2024-30261?

CVE-2024-30261 is classified as CWE-284 (CWE-284). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-30261 published, and has it been updated?

CVE-2024-30261 was published on April 4, 2024 and was last updated on October 28, 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

CVE-2024-30261 — undici

LOWFix: nodejs/undici@2b39440

CVE-2024-30261 is a low-severity (CVSS 2.6) CWE-284 vulnerability in undici. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for undici — see the affected versions and patch details below.

Undici's fetch with integrity option is too lax when algorithm is specified but hash value is in incorrect

Also known asGHSA-9qxr-qj54-h672

Published

Apr 4, 2024

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

1 known

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

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-30261.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs57th percentile — riskier than 57% 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

306.5Mdownloads / week

Description

Impact

If an attacker can alter the integrity option passed to fetch(), they can let fetch() accept requests as valid even if they have been tampered.

Patches

Fixed in https://github.com/nodejs/undici/commit/d542b8cd39ec1ba303f038ea26098c3f355974f3. Fixes has been released in v5.28.4 and v6.11.1.

Workarounds

Ensure that integrity cannot be tampered with.

References

https://hackerone.com/reports/2377760

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

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Undici is an HTTP/1.1 client, written from scratch for Node.js. An attac…

hackerone.comNVDDec 2024

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 CVE-2024-30261 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 CVE-2024-30261 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat OpenShift Dev Spaces 3 Containers	`devspaces/dashboard-rhel8:3.16-27`	RHSA-2024:6667
Red Hat Developer Hub (RHDH) 1.4	`rhdh/rhdh-hub-rhel9:1.4`	RHSA-2025:1931

Frequently Asked Questions

### Impact If an attacker can alter the `integrity` option passed to `fetch()`, they can let `fetch()` accept requests as valid even if they have been tampered. ### Patches Fixed in https://github.com/nodejs/undici/commit/d542b8cd39ec1ba303f038ea26098c3f355974f3. Fixes has been released in v5.28.4 and v6.11.1. ### Workarounds Ensure that `integrity` cannot be tampered with. ### References https://hackerone.com/reports/2377760

O3 Security · Impact-Aware SCA

Is CVE-2024-30261 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works