CVE-2026-33672: Picomatch: Method Injection in POSIX Character Classes causes incorrect Glob Matching
Medium CVSS 5.3
- OSV id
- GHSA-3v7f-55p6-f55p
- Also known as
- CVE-2026-33672
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| picomatch npm |
>= 4.0.0, < 4.0.4 | 4.0.4 |
| picomatch npm |
>= 3.0.0, < 3.0.2 | 3.0.2 |
| picomatch npm |
< 2.3.2 | 2.3.2 |
Versions we track that it affects: picomatch 2.3.1; picomatch 2.3.1; picomatch 2.3.1
How to fix it
picomatch (npm)
Upgrade picomatch to 4.0.4 or later.
npm install picomatch@4.0.4
# 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 changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
picomatch (npm)
Upgrade picomatch to 3.0.2 or later.
npm install picomatch@3.0.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 changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
picomatch (npm)
Upgrade picomatch to 2.3.2 or later.
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 changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
Not sure whether your project uses an affected version? Check your lockfile below for free.
Details
Impact
picomatch is vulnerable to a method injection vulnerability (CWE-1321) affecting the POSIX_REGEX_SOURCE object. Because the object inherits from Object.prototype, specially crafted POSIX bracket expressions (e.g., [[:constructor:]]) can reference inherited method names. These methods are implicitly converted to strings and injected into the generated regular expression.
This leads to incorrect glob matching behavior (integrity impact), where patterns may match unintended filenames. The issue does not enable remote code execution, but it can cause security-relevant logic errors in applications that rely on glob matching for filtering, validation, or access control.
All users of affected picomatch versions that process untrusted or user-controlled glob patterns are potentially impacted.
Patches
This issue is fixed in picomatch 4.0.4, 3.0.2 and 2.3.2.
Users should upgrade to one of these versions or later, depending on their supported release line.
Workarounds
If upgrading is not immediately possible, avoid passing untrusted glob patterns to picomatch.
Possible mitigations include:
- Sanitizing or rejecting untrusted glob patterns, especially those containing POSIX character classes like
[[:...:]]. - Avoiding the use of POSIX bracket expressions if user input is involved.
- Manually patching the library by modifying
POSIX_REGEX_SOURCEto use a null prototype:
```js const POSIXREGEXSOURCE = { proto: null, alnum: 'a-zA-Z0-9', alpha: 'a-zA-Z', // ... rest unchanged };
Resources
- fix for similar issue: https://github.com/micromatch/picomatch/pull/144
- picomatch repository https://github.com/micromatch/picomatch
References
- GHSA-3v7f-55p6-f55p on OSV.dev
- Web: https://github.com/micromatch/picomatch/security/advisories/GHSA-3v7f-55p6-f55p
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-33672
- Web: https://github.com/micromatch/picomatch/commit/4516eb521f13a46b2fe1a1d2c9ef6b20ddc0e903
- Package: https://github.com/micromatch/picomatch
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.