VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

re2: vulnerability history, versions and safety

re2 is a package in the npm ecosystem. Vulert records 4 vulnerabilities for it across 92 releases, from Jul 2026 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded M4
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
4 in the last 12 months

Most recent disclosure 06 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all re2 vulnerabilities

Vulert verdict on re2 1.27.0 i

Updated on 23 Oct 2026

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

Package health score 73/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 1.27.0 — unaffected i
  • Vulnerabilities on record 4 over 1 year · 4 in the last year i
  • Latest disclosure 06 Aug 2026 i
  • Highest CVSS 6.2 i
  • With no published fix 0 i
  • Depended on by 549 packages i
  • Stars 563 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence BSD-3-Clause i

Version list, release dates, licence and dependants published by the npm registry, 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 re2, 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
1.27.0 26 Sep 2026 none BSD-3-Clause — Details →
1.26.1 21 Jul 2026 none BSD-3-Clause — Details →
1.26.0 08 Jul 2026 M1 BSD-3-Clause Yes Details →
1.25.2 07 Jul 2026 M1 BSD-3-Clause Yes Details →
1.25.1 07 Jul 2026 M3 BSD-3-Clause Yes Details →
1.25.0 16 Jun 2026 M4 BSD-3-Clause Yes Details →
1.24.1 12 May 2026 M4 BSD-3-Clause Yes Details →
1.24.0 31 Mar 2026 M4 BSD-3-Clause Yes Details →
1.23.3 09 Feb 2026 M4 BSD-3-Clause Yes Details →
1.23.2 28 Jan 2026 M4 BSD-3-Clause Yes Details →
1.23.1 25 Jan 2026 M4 BSD-3-Clause Yes Details →
1.23.0 20 Dec 2025 M4 BSD-3-Clause Yes Details →
1.22.3 08 Nov 2025 M4 BSD-3-Clause Yes Details →
1.22.2 08 Nov 2025 M4 BSD-3-Clause Yes Details →
1.22.1 25 May 2025 M4 BSD-3-Clause Yes Details →
1.22.0 25 May 2025 M4 BSD-3-Clause Yes Details →
1.21.5 11 May 2025 M4 BSD-3-Clause Yes Details →
1.21.4 24 Aug 2024 M4 BSD-3-Clause Yes Details →
1.21.3 13 Jun 2024 M4 BSD-3-Clause Yes Details →
1.21.2 11 Jun 2024 M4 BSD-3-Clause Yes Details →
1.21.1 05 Jun 2024 M4 BSD-3-Clause Yes Details →
1.21.0 01 Jun 2024 M4 BSD-3-Clause Yes Details →
1.20.12 27 May 2024 M4 BSD-3-Clause Yes Details →
1.20.11 07 May 2024 M4 BSD-3-Clause Yes Details →
1.20.10 02 Mar 2024 M4 BSD-3-Clause Yes Details →
1.20.9 23 Nov 2023 M4 BSD-3-Clause Yes Details →
1.20.8 15 Nov 2023 M4 BSD-3-Clause Yes Details →
1.20.7 14 Nov 2023 M4 BSD-3-Clause Yes Details →
1.20.5 25 Oct 2023 M4 BSD-3-Clause Yes Details →
1.20.4 20 Oct 2023 M4 BSD-3-Clause Yes Details →
1.20.3 23 Aug 2023 M4 BSD-3-Clause Yes Details →
1.20.2 23 Aug 2023 M4 BSD-3-Clause Yes Details →
1.20.1 28 Jul 2023 M4 BSD-3-Clause Yes Details →
1.20.0 28 Jul 2023 M4 BSD-3-Clause Yes Details →
1.19.2 28 Jul 2023 M4 BSD-3-Clause Yes Details →
1.19.1 15 Jun 2023 M4 BSD-3-Clause Yes Details →
1.19.0 26 May 2023 M4 BSD-3-Clause Yes Details →
1.18.3 26 May 2023 M4 BSD-3-Clause Yes Details →
1.18.2 25 May 2023 M4 BSD-3-Clause Yes Details →
1.18.1 25 May 2023 M4 BSD-3-Clause Yes Details →
1.18.0 10 Dec 2022 M4 BSD-3-Clause Yes Details →
1.17.8 23 Nov 2022 M4 BSD-3-Clause Yes Details →
1.17.7 12 Jun 2022 M4 BSD-3-Clause Yes Details →
1.17.6 12 Jun 2022 M4 BSD-3-Clause Yes Details →
1.17.4 22 Feb 2022 M4 BSD-3-Clause Yes Details →
1.17.3 18 Jan 2022 M4 BSD-3-Clause Yes Details →
1.17.2 26 Dec 2021 M4 BSD-3-Clause Yes Details →
1.17.1 05 Dec 2021 M4 BSD-3-Clause Yes Details →
1.17.0 05 Dec 2021 M4 BSD-3-Clause Yes Details →
1.16.0 10 May 2021 M4 BSD-3-Clause Yes Details →
1.15.9 13 Nov 2020 M4 BSD-3-Clause Yes Details →
1.15.8 19 Oct 2020 M4 BSD-3-Clause Yes Details →
1.15.7 16 Oct 2020 M4 BSD-3-Clause Yes Details →
1.15.6 11 Oct 2020 M4 BSD-3-Clause Yes Details →
1.15.5 04 Oct 2020 M4 BSD-3-Clause Yes Details →
1.15.4 15 Jul 2020 M4 BSD-3-Clause Yes Details →
1.15.3 15 Jul 2020 M4 BSD-3-Clause Yes Details →
1.15.2 08 Jul 2020 M4 BSD-3-Clause Yes Details →
1.15.1 06 Jul 2020 M4 BSD-3-Clause Yes Details →
1.15.0 10 Jun 2020 M4 BSD-3-Clause Yes Details →
1.14.0 26 May 2020 M4 BSD-3-Clause Yes Details →
1.13.1 24 May 2020 M4 BSD-3-Clause Yes Details →
1.13.0 20 May 2020 M4 BSD-3-Clause Yes Details →
1.12.1 20 May 2020 M4 BSD-3-Clause Yes Details →
1.12.0 20 May 2020 M4 BSD-3-Clause Yes Details →
1.11.0 25 Apr 2020 M4 BSD-3-Clause Yes Details →
1.10.5 07 Dec 2019 M4 BSD-3-Clause Yes Details →
1.10.4 03 Oct 2019 M4 BSD-3-Clause Yes Details →
1.10.3 26 Sep 2019 M4 BSD-3-Clause Yes Details →
1.10.2 24 Sep 2019 M4 BSD-3-Clause Yes Details →
1.10.1 08 Sep 2019 M4 BSD-3-Clause Yes Details →
1.10.0 05 Jun 2019 M4 BSD-3-Clause Yes Details →
1.9.0 05 Jun 2019 M4 BSD-3-Clause Yes Details →
1.8.4 15 Jan 2019 M4 BSD-3-Clause Yes Details →
1.8.3 29 Sep 2018 M4 BSD-3-Clause Yes Details →
1.8.2 03 Jun 2018 M4 BSD-3-Clause Yes Details →
1.8.1 03 Jun 2018 M4 BSD-3-Clause Yes Details →
1.8.0 02 Jun 2018 M4 BSD-3-Clause Yes Details →
1.7.0 28 May 2018 M4 BSD-3-Clause Yes Details →
1.6.2 04 May 2018 M4 BSD-3-Clause Yes Details →
1.6.1 31 Jan 2018 M4 BSD-3-Clause Yes Details →
1.6.0 03 Dec 2017 M4 BSD-3-Clause Yes Details →
1.5.0 14 May 2017 M4 BSD-3-Clause Yes Details →
1.4.1 01 Dec 2016 M4 BSD-3-Clause Yes Details →
1.4.0 01 Dec 2016 M4 BSD-3-Clause Yes Details →
1.3.3 15 Apr 2016 M4 BSD-3-Clause Yes Details →
1.3.2 21 Feb 2016 M4 BSD-3-Clause Yes Details →
1.3.1 30 Aug 2015 M4 BSD-3-Clause Yes Details →
1.3.0 25 Feb 2015 M4 BSD-3-Clause Yes Details →
1.2.0 15 Dec 2014 M4 BSD-3-Clause Yes Details →
1.1.1 14 Dec 2014 M4 BSD-3-Clause Yes Details →
1.1.0 14 Dec 2014 M4 BSD-3-Clause Yes Details →
1.0.0 08 Dec 2014 M4 BSD-3-Clause Yes Details →
0.9.0 08 Dec 2014 M4 BSD-3-Clause Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 4

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

03 Vulnerabilities

Recorded vulnerabilities for re2

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-68499: re2 Package Suffers from Infinite Loop and Memory Growth Due to Global Empty Match Pattern 6.2 medium 1.25.2 31 Jul 2026
CVE-2026-71430: node-re2 Denial of Service via String.prototype.replace with Large Output 6.2 medium 1.25.1 06 Aug 2026
CVE-2026-67550: re2 Package Suffers from Out-of-Bounds Heap Read Leading to Denial of Service 5.7 medium 1.25.2 31 Jul 2026
CVE-2026-71498: node-re2 Out-of-Bounds Heap Read Vulnerability 5.1 medium 1.26.1 06 Aug 2026

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 re2

Is re2 safe to use?

Vulert records 4 vulnerabilities for re2 in npm: 0 critical, 0 high, 4 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 re2's Vulert package health score?

Vulert scores re2 73/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 re2 affected?

No. 1.27.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 re2 should I use?

1.27.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 re2 have?

4 vulnerabilities are recorded for re2 in the npm ecosystem: 0 critical, 0 high, 4 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 re2 vulnerabilities disclosed?

4 vulnerabilities were recorded for re2 in the last 12 months, and the oldest entry in this database dates to 31 Jul 2026. 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 re2 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 re2 for upcoming vulnerabilities?

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