Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven📦 npm
Not in CISA KEV
HIGH severity

GHSA-3c6g-pvg8-gqw2

HIGHFix: trentm/json#145

GHSA-3c6g-pvg8-gqw2 is a high-severity (CVSS 7.2) OS Command Injection vulnerability in org.webjars.npm:json. 3 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-3c6g-pvg8-gqw2 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

trentm/json vulnerable to command injection

Also known asCVE-2020-7712
Published
May 6, 2021
Updated
Feb 4, 2026
Affected
2 pkgs
Patched
1 / 2
Exploits
3 known
Exploitation data as of Feb 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

2 pkgs 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.

229other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
jsonnpm
316Kdownloads / week

Description

This affects the package json before 10.0.0. It is possible to inject arbritary commands using the parseLookup function.

Affected Packages

2 total 1 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.webjars.npm:jsonall versionsNo fix
📦npmjsonall versions10.0.0
Exploits & PoCs
3

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 org.webjars.npm:json. 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.

  2. Fix

    No patched version of org.webjars.npm:json has shipped for GHSA-3c6g-pvg8-gqw2 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-3c6g-pvg8-gqw2 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-3c6g-pvg8-gqw2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

This affects the package json before 10.0.0. It is possible to inject arbritary commands using the parseLookup function.
O3 Security · Impact-Aware SCA

Is GHSA-3c6g-pvg8-gqw2 in your dependencies?

O3 detects GHSA-3c6g-pvg8-gqw2 across Maven, npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-3c6g-pvg8-gqw2: trentm/json… | O3 Security