How severe is CVE-2025-57321?

No CVSS score has been assigned to CVE-2025-57321 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-57321?

CVE-2025-57321 affects the following packages: magix-combine-ex (npm). Ecosystems affected: npm.

How do I fix CVE-2025-57321?

The records we use list no patched version of magix-combine-ex for CVE-2025-57321. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2025-57321 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for magix-combine-ex, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-57321 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2025-57321 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-57321 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-57321?

CVE-2025-57321 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 38th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-57321?

CVE-2025-57321 is classified as CWE-1321 (CWE-1321). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-57321 published, and has it been updated?

CVE-2025-57321 was published on September 24, 2025 and was last updated on September 25, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2025-57321 — magix-combine-ex

CVE-2025-57321 is a CWE-1321 vulnerability in magix-combine-ex. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

magix-combine-ex vulnerable to prototype pollution

Published

Sep 24, 2025

Updated

Sep 25, 2025

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-57321.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs38th percentile — riskier than 38% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

magix-combine-exnpm

40downloads / week

Description

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

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`magix-combine-ex`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

magix-combine-exmagix-combine-ex_project

≤ 1.2.10

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for magix-combine-ex, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of magix-combine-ex for CVE-2025-57321. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-57321 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works