How severe is CVE-2021-3013?

CVE-2021-3013 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2021-3013?

CVE-2021-3013 affects the following packages: ripgrep (crates.io), grep-cli (crates.io). Ecosystems affected: crates.io.

How do I fix CVE-2021-3013?

Update ripgrep to 13.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-3013 is resolved across your whole dependency graph.

How do I detect CVE-2021-3013 in my crates.io dependencies?

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

How do I mitigate CVE-2021-3013 if there is no patch (or I can't update yet)?

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.

Is CVE-2021-3013 actively exploited in the wild?

No public exploit code has been indexed for CVE-2021-3013 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2021-3013?

CVE-2021-3013 has an EPSS (Exploit Prediction Scoring System) score of 1.9%, placing it in the 79th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2021-3013 published, and has it been updated?

CVE-2021-3013 was published on June 11, 2021 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀

🦀 crates.io

Not in CISA KEV

CRITICAL severity

CVE-2021-3013 — ripgrep

CRITICAL

CVE-2021-3013 is a critical-severity (CVSS 9.8) vulnerability in ripgrep. A fix is available for ripgrep — see the affected versions and patch details below.

OS command injection in ripgrep

Also known asGHSA-g4xg-fxmg-vcg5RUSTSEC-2021-0071

Published

Jun 11, 2021

Updated

Jul 8, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs79th percentile — riskier than 79% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2021-3013 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

2 pkgs affected

🦀ripgrep🦀grep-cli

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

ripgrep before 13 on Windows allows attackers to trigger execution of arbitrary programs from the current working directory via the -z/--search-zip or --pre flag.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`ripgrep`	all versions	13.0.0`cargo update -p ripgrep --precise 13.0.0`
🦀crates.io	`grep-cli`	all versions	0.1.6`cargo update -p grep-cli --precise 0.1.6`

Affected Products

1 product · 1 configurations

Application

ripgrepripgrep_project

< 13.0.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ripgrep, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ripgrep to 13.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-3013 is resolved across your whole dependency graph.
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.

Frequently Asked Questions

ripgrep before 13 on Windows allows attackers to trigger execution of arbitrary programs from the current working directory via the -z/--search-zip or --pre flag.

O3 Security · Impact-Aware SCA

Is CVE-2021-3013 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works