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

CVE-2020-28422 — git-archive

HIGH

CVE-2020-28422 is a high-severity (CVSS 7.8) CWE-77 vulnerability in git-archive. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

git-archive vulnerable to Command Injection via exports function

Published
Updated
Affected
1 pkg
Patched
See advisory
Exploits
None indexed
Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs38th percentile — riskier than 38% of all scored CVEsHighest risk
0.00%0.32%0.65%0.97%0.3%0.4%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.

4other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
git-archivenpm
66downloads / week

Description

All versions of package git-archive are vulnerable to Command Injection via the exports function.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmgit-archiveall versionsNo fix

Affected Products

1 product · 1 configurations
Application
git-archivegit-archive_project
all

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Remediation status

    The records we use list no patched version of git-archive for CVE-2020-28422. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

  3. Mitigate without a patch

    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

All versions of package git-archive are vulnerable to Command Injection via the exports function.
O3 Security · Impact-Aware SCA

Is CVE-2020-28422 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2020-28422: git-archive Command Injection (High 7.8)