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

CVE-2022-25900 — git-clone

HIGHFix: jaz303/git-clone@fd33045

CVE-2022-25900 is a high-severity (CVSS 8.1) CWE-88 vulnerability in git-clone. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Command injection in git-clone

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

EPSS Exploitation Probability

via FIRST.org ↗
3.9%probability of exploitation in next 30 days
Lower Risk+0.42%
Lower risk than most CVEs90th percentile — riskier than 90% of all scored CVEsHighest risk
2.73%3.55%4.37%5.20%4.7%3.9%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.

952other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
git-clonenpm
117Kdownloads / week

Description

All versions of package git-clone are vulnerable to Command Injection due to insecure usage of the --upload-pack feature of git.

Credits

Credit to @lirantal for discovering this vulnerability.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmgit-cloneall versionsNo fix

Affected Products

1 product · 1 configurations
Application
git-clonegit-clone_project
all
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.

All versions of package git-clone are vulnerable to Command Injection du…

gist.github.comNVDJul 2022

Report on snyk.io

snyk.ioNVDJul 2022

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-clone, 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-clone for CVE-2022-25900. 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-clone are vulnerable to Command Injection due to insecure usage of the `--upload-pack` feature of git. ## Credits Credit to @lirantal for discovering this vulnerability.
O3 Security · Impact-Aware SCA

Is CVE-2022-25900 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2022-25900: git-clone: Command injection