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

GHSA-h3rx-g5c9-8q4x

HIGHFix: b-heilman/bmoor@7d4a086

GHSA-h3rx-g5c9-8q4x is a high-severity (CVSS 7.3) CWE-1321 vulnerability in bmoor. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-h3rx-g5c9-8q4x is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Prototype Pollution in bmoor

Also known asCVE-2020-7736SNYK-JS-BMOOR-598664
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, a proxy for how much of the ecosystem is exposed.

bmoornpm
169downloads / week

Description

The package bmoor before 0.8.12 are vulnerable to Prototype Pollution via the set function.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmbmoorall versions0.8.12
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 bmoor. 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 bmoor to 0.8.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h3rx-g5c9-8q4x 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-h3rx-g5c9-8q4x 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-h3rx-g5c9-8q4x. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The package bmoor before 0.8.12 are vulnerable to Prototype Pollution via the set function.
O3 Security · Impact-Aware SCA

Is GHSA-h3rx-g5c9-8q4x in your dependencies?

O3 detects GHSA-h3rx-g5c9-8q4x 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-h3rx-g5c9-8q4x: Prototype Pollution in… | O3 Security