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

CVE-2020-8137 — blamer

CRITICAL

CVE-2020-8137 is a critical-severity (CVSS 9.8) Code Injection vulnerability in blamer. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for blamer — see the affected versions and patch details below.

Code injection in blamer

Also known asGHSA-7vm7-j8p7-h346
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 ↗
4.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs91th percentile — riskier than 91% of all scored CVEsHighest risk
3.66%4.18%4.70%5.21%4.7%4.3%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.

5other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
blamernpm
1.3Mdownloads / week

Description

Code injection vulnerability in blamer 1.0.0 and earlier may result in remote code execution when the input can be controlled by an attacker.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmblamerall versions1.0.1npm install blamer@1.0.1

Affected Products

1 product · 1 configurations
Application
blamerblamer_project
< 1.0.1
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.

Code injection vulnerability in blamer 1.0.0 and earlier may result in r…

hackerone.comNVDMar 2020

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

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

Code injection vulnerability in blamer 1.0.0 and earlier may result in remote code execution when the input can be controlled by an attacker.
O3 Security · Impact-Aware SCA

Is CVE-2020-8137 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2020-8137: blamer RCE — Fixed in 1.0.1