CVE-2025-22150Public exploitNetwork attack vector

Request tampering via predictable multipart boundaries

Published Jan 21, 2025 · Updated Feb 12, 2025

Insufficient randomness in Node.js Undici allows remote attackers to tamper with backend API requests through predictable multipart boundaries. Within lib/web/fetch/body.js, extractBody builds the 11-digit FormData boundary suffix with Math.random(), exposing predictable output instead of a cryptographically secure value. Exploitation requires an application to send multipart requests to an attacker-controlled site, which discloses enough PRNG output to predict a later boundary and inject data into a backend request.

CVSS severity6.8
Medium
EPSS probability0.76%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Insufficient randomness in Node.js Undici allows remote attackers to tamper with backend API requests through predictable multipart boundaries. Within lib/web/fetch/body.js, extractBody builds the 11-digit FormData boundary suffix with Math.random(), exposing predictable output instead of a cryptographically secure value. Exploitation requires an application to send multipart requests to an attacker-controlled site, which discloses enough PRNG output to predict a later boundary and inject data into a backend request.

The record

CVE
CVE-2025-22150
Published
Jan 21, 2025
Updated
Feb 12, 2025
Vendor
Node.js
Product
Undici
Classifications
CWE-330
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jan 21, 2025CVE publishedPublication date reported by the CVE source.
  2. Feb 12, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 4.5.0, < 5.28.5
  2. Affected versionversion=>= 6.0.0, < 6.21.1
  3. Affected versionversion=>= 7.0.0, < 7.2.3

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Node.js · Undiciversion=>= 4.5.0, < 5.28.5; version=>= 6.0.0, < 6.21.1; version=>= 7.0.0, < 7.2.3

Published CVSS scores

6.8GitHubCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-330Use of Insufficiently Random Values

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo