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

GHSA-gm8g-xhh8-rmwr

CRITICALFix: mrodrig/doc-path@3e2bb16

GHSA-gm8g-xhh8-rmwr is a critical-severity (CVSS 9.8) vulnerability in doc-path. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-gm8g-xhh8-rmwr is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Prototype Pollution in doc-path

Also known asCVE-2020-7772SNYK-JS-DOCPATH-1011952
Published
May 10, 2021
Updated
Jul 8, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Jul 8, 2026 · OSV.dev, NVD, 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.

5other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
doc-pathnpm
1.5Mdownloads / week

Description

This affects the package doc-path before 2.1.2.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmdoc-pathall versions2.1.2
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 doc-path. 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

    Update doc-path to 2.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gm8g-xhh8-rmwr is resolved across your whole dependency graph.

  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-gm8g-xhh8-rmwr 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-gm8g-xhh8-rmwr. 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 doc-path before 2.1.2.
O3 Security · Impact-Aware SCA

Is GHSA-gm8g-xhh8-rmwr in your dependencies?

O3 detects GHSA-gm8g-xhh8-rmwr across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-gm8g-xhh8-rmwr: Prototype Pollution… | O3 Security