VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

ripgrep: vulnerability history, versions and safety

ripgrep is a package in the crates.io ecosystem. Vulert records 1 vulnerability for it across 49 releases, first recorded in Aug 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded C1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all ripgrep vulnerabilities

Vulert verdict on ripgrep 15.2.0 i

Updated on 23 Oct 2026

Good news: 15.2.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 76/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

What to do: Stay on 15.2.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 15.2.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 15.2.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 05 Aug 2021 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Stars 69,298 i
  • OpenSSF scorecard 4/10 i
  • Last release 3 months ago i
  • Licence MIT OR Unlicense i

Version list, release dates, licence and dependants published by crates.io, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for ripgrep, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
15.2.0 15 Jul 2026 none MIT OR Unlicense — Details →
15.1.0 22 Oct 2025 none MIT OR Unlicense — Details →
15.0.0 16 Oct 2025 none MIT OR Unlicense — Details →
14.1.1 09 Sep 2024 none MIT OR Unlicense — Details →
14.1.0 06 Jan 2024 none MIT OR Unlicense — Details →
14.0.3 28 Nov 2023 none MIT OR Unlicense — Details →
14.0.2 28 Nov 2023 none MIT OR Unlicense — Details →
14.0.1 26 Nov 2023 none MIT OR Unlicense — Details →
14.0.0 26 Nov 2023 none MIT OR Unlicense — Details →
13.0.0 12 Jun 2021 none MIT OR Unlicense — Details →
12.1.1 29 May 2020 C1 MIT OR Unlicense Yes Details →
12.1.0 09 May 2020 C1 MIT OR Unlicense Yes Details →
12.0.1 29 Mar 2020 C1 MIT OR Unlicense Yes Details →
12.0.0 16 Mar 2020 C1 MIT OR Unlicense Yes Details →
11.0.2 01 Aug 2019 C1 MIT OR Unlicense Yes Details →
11.0.1 16 Apr 2019 C1 MIT OR Unlicense Yes Details →
11.0.0 16 Apr 2019 C1 MIT OR Unlicense Yes Details →
0.10.0 07 Sep 2018 C1 MIT OR Unlicense Yes Details →
0.9.0 04 Aug 2018 C1 MIT OR Unlicense Yes Details →
0.8.1 21 Feb 2018 C1 MIT OR Unlicense Yes Details →
0.8.0 12 Feb 2018 C1 MIT OR Unlicense Yes Details →
0.7.1 22 Oct 2017 C1 MIT OR Unlicense Yes Details →
0.7.0 22 Oct 2017 C1 MIT OR Unlicense Yes Details →
0.6.0 24 Aug 2017 C1 MIT OR Unlicense Yes Details →
0.5.2 12 May 2017 C1 MIT OR Unlicense Yes Details →
0.5.1 09 Apr 2017 C1 MIT OR Unlicense Yes Details →
0.5.0 13 Mar 2017 C1 MIT OR Unlicense Yes Details →
0.4.0 14 Jan 2017 C1 MIT OR Unlicense Yes Details →
0.3.2 07 Dec 2016 C1 MIT OR Unlicense Yes Details →
0.3.1 22 Nov 2016 C1 MIT OR Unlicense Yes Details →
0.3.0 21 Nov 2016 C1 MIT OR Unlicense Yes Details →
0.2.9 10 Nov 2016 C1 MIT OR Unlicense Yes Details →
0.2.8 06 Nov 2016 C1 MIT OR Unlicense Yes Details →
0.2.7 06 Nov 2016 C1 MIT OR Unlicense Yes Details →
0.2.6 01 Nov 2016 C1 MIT OR Unlicense Yes Details →
0.2.5 30 Oct 2016 C1 MIT OR Unlicense Yes Details →
0.2.4 30 Oct 2016 C1 MIT OR Unlicense Yes Details →
0.2.3 11 Oct 2016 C1 MIT OR Unlicense Yes Details →
0.2.2 11 Oct 2016 C1 MIT OR Unlicense Yes Details →
0.2.1 27 Sep 2016 C1 MIT OR Unlicense Yes Details →
0.2.0 26 Sep 2016 C1 MIT OR Unlicense Yes Details →
0.1.17 23 Sep 2016 C1 MIT OR Unlicense Yes Details →
0.1.16 23 Sep 2016 C1 MIT OR Unlicense Yes Details →
0.1.15 22 Sep 2016 C1 MIT OR Unlicense Yes Details →
0.1.14 22 Sep 2016 C1 MIT OR Unlicense Yes Details →
0.1.13 22 Sep 2016 C1 MIT OR Unlicense Yes Details →
0.1.12 22 Sep 2016 C1 MIT OR Unlicense Yes Details →
0.1.11 21 Sep 2016 C1 MIT OR Unlicense Yes Details →
0.1.10 21 Sep 2016 C1 MIT OR Unlicense Yes Details →
0.1.9 21 Sep 2016 C1 MIT OR Unlicense Yes Details →
0.1.8 21 Sep 2016 C1 MIT OR Unlicense Yes Details →
0.1.7 21 Sep 2016 C1 MIT OR Unlicense Yes Details →
0.1.6 21 Sep 2016 C1 MIT OR Unlicense Yes Details →
0.1.5 20 Sep 2016 C1 MIT OR Unlicense Yes Details →
0.1.4 18 Sep 2016 C1 MIT OR Unlicense Yes Details →
0.1.3 17 Sep 2016 C1 MIT OR Unlicense Yes Details →
0.1.2 17 Sep 2016 C1 MIT OR Unlicense Yes Details →
0.1.1 14 Sep 2016 C1 MIT OR Unlicense Yes Details →
0.1.0 14 Sep 2016 C1 MIT OR Unlicense Yes Details →

All 59 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for ripgrep

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-3013: OS Command Injection in ripgrep 9.8 critical 13.0.0 05 Aug 2021

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About ripgrep

Is ripgrep safe to use?

Vulert records 1 vulnerabilities for ripgrep in crates.io: 1 critical, 0 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is ripgrep's Vulert package health score?

Vulert scores ripgrep 76/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of ripgrep affected?

No. 15.2.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of ripgrep should I use?

15.2.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does ripgrep have?

1 vulnerability is recorded for ripgrep in the crates.io ecosystem: 1 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new ripgrep vulnerabilities disclosed?

0 vulnerabilities were recorded for ripgrep in the last 12 months, and the oldest entry in this database dates to 05 Aug 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of ripgrep are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor ripgrep for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the ripgrep version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.