Node.js undici prototype pollution in BalancedPool
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Summary
A flaw in the BalancedPool component of nodejs undici lets an attacker modify object prototype attributes. The attack can be launched remotely by someone with low-privilege login and needs no action from a user.
Written by a model
Original description
A security flaw has been discovered in nodejs undici up to 7.24.0. This affects the function Object.assign of the file balanced-pool.js of the component BalancedPool. The manipulation results in improperly controlled modification of object prototype attributes. The attack may be launched remotely. The exploit has been released to the public and may be used for attacks. Upgrading to version 7.24.1 is able to mitigate this issue. The patch is identified as 0d7ec33ff37563d3e7c98d11d7bca736f330d156. You should upgrade the affected component.
What to do
Apply the patch listed under Evidence.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133487 (nodejs undici BalancedPool balanced-pool.js Object.assign prototype pollution), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133487 (entry last updated 2026-11-20):
Affected:
- nodejs undici: versions 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6, 7.7, 7.8, 7.9, 7.10, 7.11 and 13 more
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133487 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133487 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/nodejs/undici/commit/0d7ec33ff37563d3e7c98d11d7bca736f330d156
- https://github.com/nodejs/undici/releases/tag/v7.24.1
- https://vuldb.com/vuln/440905
- https://vuldb.com/vuln/440905/cti
- https://vuldb.com/cve/CVE-2026-133487
- https://vuldb.com/submit/1049340
- https://github.com/nodejs/undici/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133487
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133487"}.Affected versions
- nodejs undici7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6, 7.7, 7.8, 7.9, 7.10, 7.11, 7.12, 7.13, 7.14, 7.15, 7.16, 7.17, 7.18, 7.19, 7.20, 7.21, 7.22, 7.23, 7.24.0
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach17/20Affects Node.js (a widely deployed server, runtime, framework or database)
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
- Would score about 44 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 10
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133487 |
| Record | NVD · CVE-2026-133487 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | GitHub · nodejs/undici · Issue #4883 |
| Other links 7 | |
| Advisory | VulDB · Advisory #440905 |
| Advisory | VulDB · Threat intelligence #440905 |
| Advisory | VulDB · CVE-2026-133487 record |
| Advisory | VulDB · Submission #1049340 |
| Patch | GitHub · nodejs/undici · Commit 0d7ec33f |
| Patch | GitHub · nodejs/undici · Release v7.24.1 |
| Repository | GitHub · nodejs/undici · Repository |
Questions about CVE-2026-133487
Is CVE-2026-133487 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-133487?
undici: versions 7.0, 7.1, 7.2, 7.3, 7.4 and 20 more.
Source: cve.now feed data
Related
- CVE-2023-24807Undici vulnerable to Regular Expression Denial of Service in Headers
- CVE-2025-22150Undici Uses Insufficiently Random Values
- CVE-2024-24750Backpressure request ignored in fetch() in Undici
- CVE-2023-23936CRLF Injection in Nodejs ‘undici’ via host
- CVE-2026-22036Undici has an unbounded decompression chain in HTTP responses on Node.js Fetch API via Content-Encoding leads to resource exhaustion
- CVE-2022-35948CRLF Injection in Nodejs ‘undici’ via Content-Type
No corrections so far. Something wrong on this page? Report an error.