PoC Monitor
← All CVEs
CVE-2026-33671published 26 Mar 2026 21:20 UTCData: JSON · API

Picomatch

Picomatch has a ReDoS vulnerability via extglob quantifiers

Picomatch is a glob matcher written JavaScript. Versions prior to 4.0.4, 3.0.2, and 2.3.2 are vulnerable to Regular Expression Denial of Service (ReDoS) when processing crafted extglob patterns. Certain patterns using extglob quantifiers such as `+()` and `*()`, especially when combined with overlapping alternatives or nested extglobs, are compiled into regular expressions that can exhibit catastrophic backtracking on non-matching input. Applications are impacted when they allow untrusted users to supply glob patterns that are passed to `picomatch` for compilation or matching. In those cases, an attacker can cause excessive CPU consumption and block the Node.js event loop, resulting in a denial of service. Applications that only use trusted, developer-controlled glob patterns are much less likely to be exposed in a security-relevant way. 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. If upgrading is not immediately possible, avoid passing untrusted glob patterns to `picomatch`. Possible mitigations include disabling extglob support for untrusted patterns by using `noextglob: true`, rejecting or sanitizing patterns containing nested extglobs or extglob quantifiers such as `+()` and `*()`, enforcing strict allowlists for accepted pattern syntax, running matching in an isolated worker or separate process with time and resource limits, and applying application-level request throttling and input validation for any endpoint that accepts glob patterns.

First public PoC 22 daysafter publication · 17 Apr 2026
Public PoCs11 on GitHub
CVSS7.5high · scored by CNA · CWE-1333
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

micromatch picomatch
  • >= 4.0.0, < 4.0.4
  • >= 3.0.0, < 3.0.2
  • < 2.3.2

Fixed in 4.0.4, 3.0.2, 2.3.2

Mitigation

Upgrade picomatch to 4.0.4 or 3.0.2 or 2.3.2 or later.

References

Timeline

Days relative to CVE publication
-3t=0+3+6+9+12+15+18+21CVE published26 Mar 2026 · t = 0First public PoC17 Apr 2026 · t+22d

First public PoC 22 days after publication; not in CISA KEV. First PoC: BeLazy167/next-picomatch-cve-repro (created 17 Apr 2026, found by us: backfilled).

PoC repositories

Found on GitHub.

1 PoCs

PoCs 1
RepositoryCreatedStarsAssessment
BeLazy167/next-picomatch-cve-repro 17 Apr 2026 +22 d 0 PoC via PoC Index

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.