magix-combine-ex vulnerable to prototype pollution

published 2025-09-24 last yr. modified 2026-06-17 4mo ago also GHSA-cr7h-93fh-whwm , EUVD-2025-31056

cvss: 9.8; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 37%
public exploits: 0; none known

A Prototype Pollution vulnerability in the util-deps.addFileDepend function of magix-combine-ex versions thru 1.2.10 allows attackers to inject properties on Object.prototype via supplying a crafted payload, causing denial of service (DoS) as the minimum consequence.

Is CVE-2025-57321 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: total
Assessed: last yr. (2025-09-26)

Exploit prediction

0.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CISA ADP	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
npm	magix-combine-ex	<=2.2.2	no fix listed

Classification

Weakness

CWE-1321 Improperly Controlled Modification of Object Prototype Attributes

References

github.com /VulnSageAgent/PoCs/blob/main/JavaScript/prototype-pollution/magix-combine-ex%401.2.10/index.js
web, broken-link
github.com /VulnSageAgent/PoCs/tree/main/JavaScript/prototype-pollution/CVE-2025-57321
web, third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2025-57321
advisory
github.com /thx/magix-combine
package

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.