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

CVE-2020-7634 — heroku-addonpool

CRITICALFix: nodef/heroku-addonpool@b1a5b31

CVE-2020-7634 is a critical-severity (CVSS 9.8) OS Command Injection vulnerability in heroku-addonpool. 2 public exploit references exist, so weaponization risk is real. A fix is available for heroku-addonpool — see the affected versions and patch details below.

OS Command Injection in heroku-addonpool

Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Oct 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs86th percentile — riskier than 86% of all scored CVEsHighest risk
2.29%2.78%3.27%3.76%3.3%2.8%Apr 26Aug 26Oct 26

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

How urgent is this, really

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

Where this sits among everything scored

Of 385,738 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.

1other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
heroku-addonpoolnpm
80downloads / week

Description

heroku-addonpool through 0.1.15 is vulnerable to Command Injection. The second parameter of the exported function HerokuAddonPool(id, app, opt) can be controlled by users without any sanitization.

PoC

var Root = require("heroku-addonpool");
var root = Root("sss", "& touch JHU", {});
root.setup();

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmheroku-addonpoolall versions0.1.16npm install heroku-addonpool@0.1.16

Affected Products

1 product · 1 configurations
Application
heroku-addonpoolheroku-addonpool_project
≤ 0.1.15
range
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

heroku-addonpool through 0.1.15 is vulnerable to Command Injection.

snyk.ioNVDJul 2021

heroku-addonpool through 0.1.15 is vulnerable to Command Injection.

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

  2. Fix

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

heroku-addonpool through 0.1.15 is vulnerable to Command Injection. The second parameter of the exported function `HerokuAddonPool(id, app, opt)` can be controlled by users without any sanitization. **PoC** ```js var Root = require("heroku-addonpool"); var root = Root("sss", "& touch JHU", {}); root.setup(); ```
O3 Security · Impact-Aware SCA

Is CVE-2020-7634 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works