CVE-2025-221506.8MediumCWE-330

CVE-2025-22150: Undici Uses Insufficiently Random Values

nodejs · undici

Affected: nodejs undici · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.8%probability of exploitation in the next 30 days

55th percentile

050100

Higher than 55% of scored CVEs

6.8MediumCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

nodejs · undici>= 4.5.0, < 5.28.5; >= 6.0.0, < 6.21.1; >= 7.0.0, < 7.2.3

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Use of Insufficiently Random Values · Cryptography
Vendor: nodejs
Published: January 2025
Band: Unlikely (under 1%), January 2025
Bounty reports: 1 disclosed on HackerOne

Disclosed bug bounty reports about CVE-2025-22150

The reports on HackerOne that name this CVE, with HackerOne's own outcome. Titles and metadata only.

Usage of unsafe random function in undici for choosing boundaryNode.js · 2025 · medium severityValid

CoverageNo articles yet

No CyberSIXT article names CVE-2025-22150 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.