Is picomatch 2.3.1 vulnerable?
picomatch 2.3.1, a JavaScript package on npm. All 4 versions we track · npm page
Upgrade picomatch from 2.3.1 to 2.3.2 or later; that fixes all of them.
Known vulnerabilities in picomatch 2.3.1
-
High
CVSS 7.5
CVE-2026-33671: Picomatch has a ReDoS vulnerability via extglob quantifiers
GHSA-c2c7-rcm5-vvqj · published 25 Mar 2026 · fixed in 2.3.2
-
Medium
CVSS 5.3
CVE-2026-33672: Picomatch: Method Injection in POSIX Character Classes causes incorrect Glob Matching
GHSA-3v7f-55p6-f55p · published 25 Mar 2026 · fixed in 2.3.2
How to fix it
With package-lock.json:
npm install picomatch@2.3.2
# if it is an indirect dependency: npm update picomatch (or npm audit fix)
- If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
- Check the package's changelog for breaking changes (especially across major versions), update the lockfile with the package manager (never by hand), and run your tests.
Other versions of picomatch
Newest version we track without known advisories: 4.0.7.
Licence
picomatch 2.3.1 declares MIT .
Check your whole project
picomatch is one package among hundreds in a lockfile. Upload your lockfile, or paste a public GitHub repository, and get every vulnerable package with the version that fixes it. Free, and no account needed.
Get emailed about new advisories for picomatch (free, no account)
About this data
Vulnerability data: OSV.dev, last checked 22 November 2026. Licence: deps.dev. AIssue checks the versions on this page every day. Severity comes from the advisory's own rating when it has one, else from its CVSS score.