Undici Uses Insufficiently Random Values
cve-program · CVE-2025-22150
PublishedUndici 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.
Read the publisher's advisoryeuvd · EUVD-2025-0154
PublishedUndici 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.
Read the publisher's advisorynvd · CVE-2025-22150
PublishedUndici 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.
Read the publisher's advisoryosv · GHSA-c76h-2ccp-4975
Published### Impact [Undici `fetch()` uses Math.random()](https://github.com/nodejs/undici/blob/8b06b8250907d92fead664b3368f1d2aa27c1f35/lib/web/fetch/body.js#L113) 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. ### Patches This is fixed in 5.28.5; 6.21.1; 7.2.3. ### Workarounds Do not issue multipart requests to attacker controlled servers. ### References * https://hackerone.com/reports/2913312 * https://blog.securityevaluators.com/hacking-the-javascript-lottery-80cc437e3b7f
Read the publisher's advisoryAffected versions, risk and source history
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
cve-program · CVE-2025-22150
PublishedUndici Uses Insufficiently Random Values
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.
- Source published
- 21 Jan 2025 17:46:58 UTC
- Source modified
- 12 Feb 2025 20:41:22 UTC
- Saved here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · 6.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
euvd · EUVD-2025-0154
PublishedUndici 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()` ca…
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.
Additional publisher context
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Jan 21, 2025, 5:46:58 PM
dateUpdated: Feb 12, 2025, 8:41:22 PM
26 related source bulletins · separate from aliases
RHSA-2025:1351: Red Hat Security Advisory: nodejs:20 security update
CVE-2025-22150 · CVE-2025-23083 · CVE-2025-23085
openSUSE-SU-2026:11110-1: nodejs26-26.3.1-1.1 on GA media
CVE-2024-21538 · CVE-2024-22018 · CVE-2024-22020 · CVE-2024-36137 · CVE-2024-36138 · CVE-2024-37372 · CVE-2025-22150 · CVE-2025-23083 · CVE-2025-23085 · CVE-2025-23165 · CVE-2025-23166 · CVE-2025-55130 · CVE-2025-55131 · CVE-2025-55132 · CVE-2025-59464 · CVE-2025-59465 · CVE-2025-59466 · CVE-2026-21637 · CVE-2026-21710 · CVE-2026-21712 · CVE-2026-21713 · CVE-2026-21714 · CVE-2026-21715 · CVE-2026-21716 · CVE-2026-21717 · CVE-2026-22036 · CVE-2026-48615 · CVE-2026-48617 · CVE-2026-48618 · CVE-2026-48619 · CVE-2026-48928 · CVE-2026-48930 · CVE-2026-48931 · CVE-2026-48933 · CVE-2026-48934 · CVE-2026-48935 · CVE-2026-48936
RHSA-2025:3368: Red Hat Security Advisory: RHOAI 2.16.0 - Red Hat OpenShift AI
CVE-2024-21538 · CVE-2024-45296 · CVE-2024-45338 · CVE-2024-45339 · CVE-2024-52798 · CVE-2024-55565 · CVE-2024-56171 · CVE-2024-56201 · CVE-2025-22150 · CVE-2025-24928 · CVE-2025-26791
openSUSE-SU-2025:14706-1: corepack22-22.13.0-1.1 on GA media
CVE-2025-22150 · CVE-2025-23083 · CVE-2025-23085
SUSE-SU-2025:0237-1: Security update for nodejs20
CVE-2025-22150 · CVE-2025-23083 · CVE-2025-23085
SUSE-SU-2025:0232-1: Security update for nodejs20
CVE-2025-22150 · CVE-2025-23083 · CVE-2025-23085
RHSA-2025:3374: Red Hat Security Advisory: Red Hat Developer Hub 1.5.1 release.
CVE-2024-45338 · CVE-2024-47068 · CVE-2024-52798 · CVE-2024-55565 · CVE-2024-56201 · CVE-2024-56326 · CVE-2024-56334 · CVE-2025-22150 · CVE-2025-27516 · CVE-2025-29774 · CVE-2025-29775
WID-SEC-W-2025-0156: Node.js: Mehrere Schwachstellen
CVE-2025-22150 · CVE-2025-23083 · CVE-2025-23084 · CVE-2025-23085 · CVE-2025-23087 · CVE-2025-23088 · CVE-2025-23089
SUSE-SU-2026:3929-1: Security update for nodejs20
CVE-2025-22150 · CVE-2026-11525 · CVE-2026-12151 · CVE-2026-16728 · CVE-2026-16729 · CVE-2026-22036 · CVE-2026-27135 · CVE-2026-40170 · CVE-2026-42338 · CVE-2026-48615 · CVE-2026-48617 · CVE-2026-48618 · CVE-2026-48619 · CVE-2026-48928 · CVE-2026-48930 · CVE-2026-48931 · CVE-2026-48933 · CVE-2026-48934 · CVE-2026-48935 · CVE-2026-48937 · CVE-2026-54272 · CVE-2026-56846 · CVE-2026-56847 · CVE-2026-56848 · CVE-2026-56850 · CVE-2026-58039 · CVE-2026-58040 · CVE-2026-58042 · CVE-2026-58043 · CVE-2026-58044 · CVE-2026-58045 · CVE-2026-6733 · CVE-2026-69192 · CVE-2026-9496 · CVE-2026-9679
RHSA-2025:3397: Red Hat Security Advisory: RHOAI 2.16.0 - Red Hat OpenShift AI
CVE-2024-21538 · CVE-2024-45296 · CVE-2024-45338 · CVE-2024-45339 · CVE-2024-52798 · CVE-2024-55565 · CVE-2024-56171 · CVE-2024-56201 · CVE-2025-22150 · CVE-2025-24928 · CVE-2025-26791
SUSE-SU-2025:0233-1: Security update for nodejs18
CVE-2025-22150 · CVE-2025-23085
RHSA-2025:2588: Red Hat Security Advisory: RHOAI 2.18.0 - Red Hat OpenShift AI
CVE-2024-11187 · CVE-2024-45337 · CVE-2024-45338 · CVE-2025-22150 · CVE-2025-24970
RHSA-2025:1613: Red Hat Security Advisory: nodejs:22 security update
CVE-2025-22150 · CVE-2025-23083 · CVE-2025-23085
RHSA-2025:1582: Red Hat Security Advisory: nodejs:18 security update
CVE-2025-22150 · CVE-2025-23085
RHSA-2025:17145: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.17 security, enhancement & bug fix update
CVE-2025-22150
RHSA-2025:1443: Red Hat Security Advisory: nodejs:20 security update
CVE-2025-22150 · CVE-2025-23083 · CVE-2025-23085
SUSE-SU-2025:0234-1: Security update for nodejs18
CVE-2025-22150 · CVE-2025-23085
SUSE-SU-2025:0284-1: Security update for nodejs22
CVE-2025-22150 · CVE-2025-23083 · CVE-2025-23085
openSUSE-SU-2025:15802-1: corepack24-24.11.1-2.1 on GA media
CVE-2024-21538 · CVE-2024-22018 · CVE-2024-22020 · CVE-2024-36137 · CVE-2024-36138 · CVE-2024-37372 · CVE-2025-22150 · CVE-2025-23083 · CVE-2025-23085 · CVE-2025-23165 · CVE-2025-23166
RHSA-2025:21368: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.18 security, enhancement & bug fix update
CVE-2022-0155 · CVE-2022-0536 · CVE-2025-5889 · CVE-2025-7195 · CVE-2025-22150
RHSA-2025:1611: Red Hat Security Advisory: nodejs:22 security update
CVE-2025-22150 · CVE-2025-23083 · CVE-2025-23085
RHSA-2025:1446: Red Hat Security Advisory: nodejs:18 security update
CVE-2025-22150 · CVE-2025-23085
SUSE-SU-2026:4248-1: Security update for nodejs18
CVE-2025-22150 · CVE-2025-23166 · CVE-2025-23167 · CVE-2025-55131 · CVE-2025-59465 · CVE-2025-59466 · CVE-2025-62408 · CVE-2026-11525 · CVE-2026-12151 · CVE-2026-15157 · CVE-2026-16728 · CVE-2026-16729 · CVE-2026-21637 · CVE-2026-21710 · CVE-2026-21713 · CVE-2026-21714 · CVE-2026-21717 · CVE-2026-22036 · CVE-2026-27135 · CVE-2026-48618 · CVE-2026-48619 · CVE-2026-48928 · CVE-2026-48930 · CVE-2026-48931 · CVE-2026-48933 · CVE-2026-48934 · CVE-2026-48935 · CVE-2026-48937 · CVE-2026-56846 · CVE-2026-56848 · CVE-2026-56850 · CVE-2026-58040 · CVE-2026-58042 · CVE-2026-58043 · CVE-2026-58044 · CVE-2026-58045 · CVE-2026-6733 · CVE-2026-9679
SUSE-SU-2026:3930-1: Security update for nodejs20
CVE-2025-22150 · CVE-2026-11525 · CVE-2026-12151 · CVE-2026-16728 · CVE-2026-16729 · CVE-2026-22036 · CVE-2026-27135 · CVE-2026-40170 · CVE-2026-42338 · CVE-2026-48615 · CVE-2026-48617 · CVE-2026-48618 · CVE-2026-48619 · CVE-2026-48928 · CVE-2026-48930 · CVE-2026-48931 · CVE-2026-48933 · CVE-2026-48934 · CVE-2026-48935 · CVE-2026-48937 · CVE-2026-54272 · CVE-2026-56846 · CVE-2026-56847 · CVE-2026-56848 · CVE-2026-56850 · CVE-2026-58039 · CVE-2026-58040 · CVE-2026-58042 · CVE-2026-58043 · CVE-2026-58044 · CVE-2026-58045 · CVE-2026-6733 · CVE-2026-69192 · CVE-2026-9496 · CVE-2026-9679
RHSA-2025:1931: Red Hat Security Advisory: Red Hat Developer Hub 1.4.2 release.
CVE-2024-30261 · CVE-2025-22150
msrc_CVE-2025-22150: Undici Uses Insufficiently Random Values
CVE-2025-22150
- Source published
- Jan 21, 2025, 5:46:58 PM (timezone not stated)
- Source modified
- Feb 12, 2025, 8:41:22 PM (timezone not stated)
- Saved here
- 13 Nov 2026 21:10:40 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
EUVD CVSS 3.1 · 6.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
nvd · CVE-2025-22150
PublishedUndici 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()` ca…
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.
Additional publisher context
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Deferred
Weakness classifications: CWE-330
Original publisher date fields
published: 2025-01-21T18:15:14.887
lastModified: 2026-06-17T08:45:21.600
- Source published
- 21 Jan 2025 18:15:14 UTC
- Source modified
- 17 Jun 2026 08:45:21 UTC
- Saved here
- 25 Oct 2026 01:17:29 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · [email protected] · Secondary · 6.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
osv · GHSA-c76h-2ccp-4975
PublishedUse of Insufficiently Random Values in undici
### Impact [Undici `fetch()` uses Math.random()](https://github.com/nodejs/undici/blob/8b06b8250907d92fead664b3368f1d2aa27c1f35/lib/web/fetch/body.js#L113) 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. ### Patches This is fixed in 5.28.5; 6.21.1; 7.2.3. ### Workarounds Do not issue multipart requests to attacker controlled servers. ### References * https://hackerone.com/reports/2913312 * https://blog.securityevaluators.com/hacking-the-javascript-lottery-80cc437e3b7f
- Source published
- 21 Jan 2025 21:10:47 UTC
- Source modified
- 10 Sep 2026 03:50:56 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V3 · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
Publisher rating · MODERATE