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

CVE-2020-7605

CRITICAL

CVE-2020-7605 is a critical-severity (CVSS 9.8) OS Command Injection vulnerability in gulp-tape. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2020-7605 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OS Command Injection in gulp-tape

Also known asGHSA-x67x-98x7-wv26SNYK-JS-GULPTAPE-560124
Published
Mar 15, 2020
Updated
Jul 9, 2026
Affected
1 pkg
Patched
None yet
Exploits
1 known
Exploitation data as of Jul 9, 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, 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
gulp-tapenpm
464downloads / week

Description

gulp-tape through 1.0.0 allows execution of arbitrary commands. It is possible to inject arbitrary commands as part of 'gulp-tape' options.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmgulp-tapeall versionsNo fix
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 gulp-tape. 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. Remediation status

    No patched version of gulp-tape has shipped for CVE-2020-7605 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    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 CVE-2020-7605 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 CVE-2020-7605. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

gulp-tape through 1.0.0 allows execution of arbitrary commands. It is possible to inject arbitrary commands as part of 'gulp-tape' options.
O3 Security · Impact-Aware SCA

Is CVE-2020-7605 in your dependencies?

O3 detects CVE-2020-7605 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

CVE-2020-7605: OS Command Injection in… | O3 Security