GHSA-x2fc-mxcx-w4mf
HIGHGHSA-x2fc-mxcx-w4mf is a high-severity (CVSS 7.3) CWE-1321 vulnerability in mathjs. 4 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-x2fc-mxcx-w4mf is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Prototype Pollution in mathjs
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
mathjsnpmDescription
The package mathjs before 7.5.1 are vulnerable to Prototype Pollution via the deepExtend function that runs upon configuration updates.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | mathjs | all versions | 7.5.1 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
The package mathjs before 7.5.1 are vulnerable to Prototype Pollution vi…
The package mathjs before 7.5.1 are vulnerable to Prototype Pollution vi…
The package mathjs before 7.5.1 are vulnerable to Prototype Pollution vi…
The package mathjs before 7.5.1 are vulnerable to Prototype Pollution vi…
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mathjs. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update mathjs to 7.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x2fc-mxcx-w4mf is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-x2fc-mxcx-w4mf is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-x2fc-mxcx-w4mf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-x2fc-mxcx-w4mf in your dependencies?
O3 detects GHSA-x2fc-mxcx-w4mf across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.