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

CVE-2020-7736 — bmoor

CRITICALFix: b-heilman/bmoor@7d4a086

CVE-2020-7736 is a critical-severity (CVSS 9.8) CWE-1321 vulnerability in bmoor. 1 public exploit reference exists, so weaponization risk is real. A fix is available for bmoor — see the affected versions and patch details below.

Prototype Pollution in bmoor

Also known asGHSA-h3rx-g5c9-8q4xSNYK-JS-BMOOR-598664
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs73th percentile — riskier than 73% of all scored CVEsHighest risk
0.35%0.89%1.43%1.97%0.8%1.5%Apr 26Aug 26Oct 26

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

How urgent is this, really

CVE-2020-7736 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

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.

9other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
bmoornpm
2Kdownloads / 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.12npm install bmoor@0.8.12

Affected Products

1 product · 1 configurations
Application
bmoorbmoor_project
< 0.8.12
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.

The package bmoor before 0.8.12 are vulnerable to Prototype Pollution vi…

snyk.ioNVDJul 2021

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update bmoor to 0.8.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-7736 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.

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 CVE-2020-7736 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works