VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

picomatch: vulnerability history, versions and safety

picomatch is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 4 releases, first recorded in Mar 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded H2 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 25 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all picomatch vulnerabilities

Vulert verdict on picomatch 4.0.7 i

Updated on 23 Oct 2026

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

Package health score 79/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 4.0.7 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 3 in the last year i
  • Latest disclosure 25 Mar 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 183,098 packages i
  • Stars 1,302 i
  • OpenSSF scorecard 5/10 i
  • Last release 1 month ago i
  • Licence MIT 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 picomatch, 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
4.0.7 24 Aug 2026 none MIT — Details →
4.0.6 24 Aug 2026 none MIT — Details →
4.0.5 02 Jul 2026 none MIT — Details →
4.0.4 23 Mar 2026 none MIT — Details →
3.0.2 23 Mar 2026 none MIT — Details →
2.3.2 23 Mar 2026 none MIT — Details →
4.0.3 15 Jul 2025 H2 M1 MIT Yes Details →
4.0.2 28 Mar 2024 H2 M1 MIT Yes Details →
4.0.1 08 Feb 2024 H2 M1 MIT Yes Details →
4.0.0 08 Feb 2024 H2 M1 MIT Yes Details →
3.0.1 29 Oct 2023 none MIT — Details →
3.0.0 29 Oct 2023 none MIT — Details →
2.3.1 02 Jan 2022 none MIT — Details →
2.3.0 22 May 2021 none MIT — Details →
2.2.3 10 Apr 2021 none MIT — Details →
2.2.2 21 Mar 2020 none MIT — Details →
2.2.1 04 Jan 2020 none MIT — Details →
2.2.0 04 Jan 2020 none MIT — Details →
2.1.1 06 Nov 2019 none MIT — Details →
2.1.0 31 Oct 2019 none MIT — Details →
2.0.7 14 May 2019 none MIT — Details →
2.0.6 04 May 2019 none MIT — Details →
2.0.5 20 Apr 2019 none MIT — Details →
2.0.4 14 Apr 2019 none MIT — Details →
2.0.3 10 Apr 2019 none MIT — Details →
2.0.2 10 Apr 2019 none MIT — Details →
2.0.1 10 Apr 2019 none MIT — Details →
2.0.0 10 Apr 2019 none MIT — Details →
1.2.0 30 Mar 2019 none MIT — Details →
1.1.2 15 Dec 2018 none MIT — Details →
1.1.1 15 Dec 2018 none MIT — Details →
1.1.0 14 Dec 2018 none MIT — Details →
1.0.2 05 Nov 2018 none MIT — Details →
1.0.1 05 Nov 2018 none MIT — Details →
1.0.0 05 Nov 2018 none MIT — Details →

All 35 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 3

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

03 Vulnerabilities

Recorded vulnerabilities for picomatch

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-33671: Picomatch ReDoS Vulnerability via Extglob Quantifiers 7.5 high 4.0.4 25 Mar 2026
CVE-2026-33671: Picomatch ReDoS Vulnerability via Extglob Quantifiers 7.5 high 4.0.4 25 Mar 2026
CVE-2026-33672: Picomatch Method Injection Vulnerability Leading to Incorrect Glob Matching 5.3 medium 4.0.4 25 Mar 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 picomatch

Is picomatch safe to use?

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

Vulert scores picomatch 79/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 picomatch affected?

No. 4.0.7, 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 picomatch should I use?

4.0.7 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 picomatch have?

3 vulnerabilities are recorded for picomatch in the npm ecosystem: 0 critical, 2 high, 1 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 picomatch vulnerabilities disclosed?

3 vulnerabilities were recorded for picomatch in the last 12 months, and the oldest entry in this database dates to 25 Mar 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 picomatch 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 picomatch for upcoming vulnerabilities?

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