NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

Code Injection in metacalcGHSA-5gc4-cx9x-9c43

CRITICALFix: metarhia/metacalc#16

GHSA-5gc4-cx9x-9c43 is a critical-severity (CVSS 9) Code Injection vulnerability in metacalc. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for metacalc — see the affected versions and patch details below.

Also known asCVE-2022-21122SNYK-JS-METACALC-2826197
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs86th percentile — riskier than 86% of all scored CVEsHighest risk
0.33%1.29%2.26%3.23%0.9%2.7%May 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

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
metacalcnpm
71downloads / week

Description

The package metacalc before 0.0.2 are vulnerable to Arbitrary Code Execution when it exposes JavaScript's Math class to the v8 context. As the Math class is exposed to user-land, it can be used to get access to JavaScript's Function constructor.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmmetacalcall versions0.0.2npm install metacalc@0.0.2

Affected Products

1 product · 1 configurations
Application
metacalcmetarhia
< 0.0.2
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update metacalc to 0.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5gc4-cx9x-9c43 is resolved across your whole dependency graph.

  3. Workarounds

    Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

The package metacalc before 0.0.2 is vulnerable to Arbitrary Code Execution when it exposes JavaScript's Math class to the v8 context. As the Math class is exposed to user-land, it can be used to get access to JavaScript's Function constructor.
O3 Security · Impact-Aware SCA

Is GHSA-5gc4-cx9x-9c43 in your dependencies?

Find it across npm, including transitive dependencies.

Code Injection in metacalc (Critical 9)