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

GHSA-8cxp-cjm8-fj36

CRITICALFix: kucherenko/blamer@5fada8c

GHSA-8cxp-cjm8-fj36 is a critical-severity (CVSS 9.8) OS Command Injection vulnerability in blamer. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-8cxp-cjm8-fj36 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Improper Neutralization of Special Elements used in an OS Command in Blamer

Also known asCVE-2019-10807SNYK-JS-BLAMER-559541
Published
May 24, 2022
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.

blamernpm
1.4Mdownloads / week

Description

Blamer versions prior to 1.0.1 allows execution of arbitrary commands. It is possible to inject arbitrary commands as part of the arguments provided to blamer.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmblamerall versions1.0.1
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 blamer. 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 blamer to 1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8cxp-cjm8-fj36 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-8cxp-cjm8-fj36 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-8cxp-cjm8-fj36. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Blamer versions prior to 1.0.1 allows execution of arbitrary commands. It is possible to inject arbitrary commands as part of the arguments provided to blamer.
O3 Security · Impact-Aware SCA

Is GHSA-8cxp-cjm8-fj36 in your dependencies?

O3 detects GHSA-8cxp-cjm8-fj36 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-8cxp-cjm8-fj36: blamer (Critical 9.8) | O3 Security