CVE-2025-22150

MEDIUMNVD 6.86.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 6.8 from GitHub Security Advisory (severity: MODERATE) published 2025-01-21. NVD baseline CVSS 6.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2025-0154 (ENISA EUVD) · GHSA-c76h-2ccp-4975 (GitHub Security Advisories)Source: ENISA EUVD

6.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 6.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Undici is an HTTP/1.1 client. Starting in version 4.5.0 and prior to versions 5.28.5, 6.21.1, and 7.2.3, undici uses Math.random() to choose the boundary for a multipart/form-data request. It is known that the output of Math.random() can be predicted if several of its generated values are known. If there is a mechanism in an app that sends multipart requests to an attacker-controlled website, they can use this to leak the necessary values. Therefore, an attacker can tamper with the requests going to the backend APIs if certain conditions are met. This is fixed in versions 5.28.5, 6.21.1, and 7.2.3. As a workaround, do not issue multipart requests to attacker controlled servers.

CVSS v3
6.8
EG Score
6.8MEDIUMmedium confidence
EG Risk
47
EG Risk 47/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity68% × 45%
Impact severity (EG Severity): CVSS 6.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.8%
EPSS %ILE
55th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.8): severity, escalated by confirmed exploitation. This CVE's 6.8 is its impact severity (EG Severity), not escalated.

EG Severity
6.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

January 21, 2025

Last Modified

April 15, 2026

Advisory Details (6)

Auto-updated Oct 24, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Use of Insufficiently Random Values in undici fetch() · Advisory · nodejs/undici · GitHub

Affected: 5.28.5; 6.21.1; 7.2.3.

https://github.com/nodejs/undici/security/advisories/GHSA-c76h-2ccp-4975
GitHub commit Patch Available

commit c3acc6050b78 (nodejs/undici)

Patch available: nodejs/undici v6.27.0 (contains commit c3acc6050b78)

https://github.com/nodejs/undici/commit/c3acc6050b781b827d80c86cbbab34f14458d385
GitHub commit Patch Available

commit c2d78cd19fe4 (nodejs/undici)

Patch available: nodejs/undici v7.27.0 (contains commit c2d78cd19fe4)

https://github.com/nodejs/undici/commit/c2d78cd19fe4f4c621424491e26ce299e65e934a
GitHub commit

commit 711e20772764 (nodejs/undici)

Fix landed in nodejs/undici commit 711e20772764 — awaiting tagged release

https://github.com/nodejs/undici/commit/711e20772764c29f6622ddc937c63b6eefdf07d0
Web page

undici/lib/web/fetch/body.js at 8b06b8250907d92fead664b3368f1d2aa27c1f35 · nodejs/undici · GitHub

https://github.com/nodejs/undici/blob/8b06b8250907d92fead664b3368f1d2aa27c1f35/lib/web/fetch/body.js#L113

Patch Availability(16)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatodf4/rook-ceph-rhel9-operator:v4.18-17618552342025-11-13redhat
redhatodf4/rook-ceph-rhel9-operator:v4.17-17576055182025-10-01redhat
redhatrhoai/odh-dashboard-rhel8:v2.16.2-17419631522025-03-31redhat
redhatrhdh/rhdh-hub-rhel9:1.52025-03-27redhat
redhatrhoai/odh-dashboard-rhel8:v2.18.0-17409902972025-03-10redhat
redhatrhdh/rhdh-hub-rhel9:1.42025-02-27redhat
redhatnodejs:18-8100020250207121904.489197e62025-02-17redhat
redhatnodejs:22-9050020250131131518.rhel92025-02-17redhat
redhatnodejs:22-8100020250130144944.6d8804032025-02-17redhat
redhatnodejs:18-9050020250206154514.rhel92025-02-13redhat
redhatrhdh-hub-container-1.3-1422025-02-13redhat
redhatnodejs:20-9050020250130114516.rhel92025-02-13redhat
redhatnodejs:20-8100020250203134842.489197e62025-02-12redhat
npmundici @ 5.28.5 (fixes >= 4.5.0, < 5.28.5)—ghsa
npmundici @ 6.21.1 (fixes >= 6.0.0, < 6.21.1)—ghsa
npmundici @ 7.2.3 (fixes >= 7.0.0, < 7.2.3)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(8 across 8 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 22.13.1-r0: fixed in 22.13.1-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 22.13.1-r0: fixed in 22.13.1-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 22.13.1-r0: fixed in 22.13.1-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 22.13.1-r0: fixed in 22.13.1-r0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-undici5.15.0+dfsg1+~cs20.10.9.3-1 ... 8.9.0+dfsg+~cs3.2.0-1 (39 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-undici—
  • every version up to 7.3.0+dfsg1+~cs24.12.11-1: fixed in 7.3.0+dfsg1+~cs24.12.11-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-undici—
  • every version up to 7.3.0+dfsg1+~cs24.12.11-1: fixed in 7.3.0+dfsg1+~cs24.12.11-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
undici—
  • 4.5.0 up to 5.28.5: fixed in 5.28.5
  • 6.0.0 up to 6.21.1: fixed in 6.21.1
  • 7.0.0 up to 7.2.3: fixed in 7.2.3
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 9× in last 7d / 40× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 229 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 133 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  2. 2026-11-01 08:09 UTCGHSA enrichmentGHSA-c76h-2ccp-4975 · GitHub severity MODERATE · GitHub CVSS 6.8
  3. 2026-11-01 08:09 UTCEG score recompute
  4. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  5. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  6. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  7. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  8. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  9. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  10. 2026-10-25 16:42 UTCEG score recompute
  11. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  12. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  13. 2026-10-24 01:08 UTCEG score recompute
  14. 2026-10-24 01:08 UTCVendor advisory
  15. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  16. 2026-10-22 16:32 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  17. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  18. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  19. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  20. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  21. 2026-10-18 05:45 UTCEG score recompute
  22. 2026-10-17 16:32 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  23. 2026-10-16 16:38 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  24. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  25. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.8% · 54th percentile
Show 71 more
  1. 2026-10-13 16:32 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  2. 2026-10-12 17:19 UTCEG score recompute
  3. 2026-10-12 16:32 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  4. 2026-10-11 20:50 UTCEG score recompute
  5. 2026-10-11 19:01 UTCEG score recompute
  6. 2026-10-11 15:41 UTCEG score recompute
  7. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  8. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  9. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  10. 2026-10-08 17:09 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  11. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  12. 2026-10-07 02:24 UTCOSV refresh
  13. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  14. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  15. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  16. 2026-10-02 16:26 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  17. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  18. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  19. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  20. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  21. 2026-09-26 00:24 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  22. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  23. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  24. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  25. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  26. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  27. 2026-09-17 08:06 UTCOSV refresh
  28. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  29. 2026-09-16 05:13 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  30. 2026-09-15 03:09 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  31. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  32. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  33. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  34. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  35. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  36. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  37. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  38. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  39. 2026-09-05 15:28 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  40. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  41. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  42. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  43. 2026-09-01 04:38 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  44. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  45. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  46. 2026-08-29 08:43 UTCOSV refresh
  47. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  48. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  49. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  50. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  51. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  52. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  53. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  54. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  55. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  56. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  57. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  58. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  59. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  60. 2026-08-12 20:01 UTCOSV refresh
  61. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  62. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  63. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  64. 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  65. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  66. 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  67. 2026-08-04 15:09 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  68. 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  69. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  70. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  71. 2026-08-01 04:15 UTCEPSS rescoreEPSS 0.7% · 51st percentile

Frequently asked(5)

What is CVE-2025-22150?
CVE-2025-22150 is a medium-severity vulnerability; its CVE record was published on January 21, 2025. Undici is an HTTP/1.1 client. Starting in version 4.5.0 and prior to versions 5.28.5, 6.21.1, and 7.2.3, undici uses Math.random() to choose the boundary for a multipart/form-data request. It is known that the output of Math.random() can be predicted if several of its generated values are known. If…
When was the CVE record for CVE-2025-22150 published?
The CVE record for CVE-2025-22150 was published on January 21, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 15, 2026; the record at its source may have been updated since.
Is CVE-2025-22150 actively exploited?
CVE-2025-22150 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-22150?
CVE-2025-22150 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2025-22150?
A fix for CVE-2025-22150 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-22150 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-22150

Explore →

Is Your Infrastructure Affected by CVE-2025-22150?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.