picomatch

Ecosystem: npm

Downloads:

Vulnerabilities from the last (months)
  • 0CriticalAffects 0 versions
  • 2HighAffects 4 versions
  • 0MediumAffects 0 versions
  • 1ModerateAffects 3 versions
  • 0LowAffects 0 versions
Severity distribution (all time)
3vulnerabilities
  • Critical0 (0.0%)
  • High2 (66.7%)
  • Medium0 (0.0%)
  • Moderate1 (33.3%)
  • Low0 (0.0%)

Monthly breakdown

  • Critical
  • High
  • Medium
  • Moderate
  • Low
  • 1 vulnerabilities
    • Critical: 0
    • High: 1
    • Medium: 0
    • Moderate: 0
    • Low: 0
  • 2 vulnerabilities
    • Critical: 0
    • High: 1
    • Medium: 0
    • Moderate: 1
    • Low: 0

Vulnerabilities (3)

Known vulnerabilities affecting picomatch, based on data from OSV.

Vulnerabilities affecting picomatch
IDSeveritySummaryAffected versionsPublishedSource
GHSA-fc5q-39xc-vjpfHighpicomatch vulnerable to ReDoS through single-branch repeated extglobsPicomatch through 4.0.7 contains a regular expression denial of service vulnerability that allows attackers to block the event loop by supplying single-branch repeated extglob patterns. Attackers can provide globs like +(*) or +(*a), which analyzeRepeatedExtglob in lib/parse.js skips, causing exponential backtracking against short crafted strings and denying service to Node.js applications.
  • <= 4.0.7
GitHub (opens in a new tab)
GHSA-3v7f-55p6-f55pModeratePicomatch: Method Injection in POSIX Character Classes causes incorrect Glob Matching### 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
  • >= 4.0.0, < 4.0.4
  • >= 3.0.0, < 3.0.2
  • < 2.3.2
GitHub (opens in a new tab)
GHSA-c2c7-rcm5-vvqjHighPicomatch has a ReDoS vulnerability via extglob quantifiers### Impact `picomatch` is 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. Examples of problematic patterns include `+(a|aa)`, `+(*|?)`, `+(+(a))`, `*(+(a))`, and `+(+(+(a)))`. In local reproduction, these patterns caused multi-second event-loop blocking with relatively short inputs. For example, `+
  • >= 4.0.0, < 4.0.4
  • >= 3.0.0, < 3.0.2
  • < 2.3.2
GitHub (opens in a new tab)
  • GHSA-fc5q-39xc-vjpfHigh
    picomatch vulnerable to ReDoS through single-branch repeated extglobs
    • <= 4.0.7

    Picomatch through 4.0.7 contains a regular expression denial of service vulnerability that allows attackers to block the event loop by supplying single-branch repeated extglob patterns. Attackers can provide globs like +(*) or +(*a), which analyzeRepeatedExtglob in lib/parse.js skips, causing exponential backtracking against short crafted strings and denying service to Node.js applications.

    CVE: CVE-2026-112366

  • GHSA-3v7f-55p6-f55pModerate
    Picomatch: Method Injection in POSIX Character Classes causes incorrect Glob Matching
    • >= 4.0.0, < 4.0.4
    • >= 3.0.0, < 3.0.2
    • +1 more
    Affected versions:
    • >= 4.0.0, < 4.0.4
    • >= 3.0.0, < 3.0.2
    • < 2.3.2

    ### 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

    CVE: CVE-2026-33672

  • GHSA-c2c7-rcm5-vvqjHigh
    Picomatch has a ReDoS vulnerability via extglob quantifiers
    • >= 4.0.0, < 4.0.4
    • >= 3.0.0, < 3.0.2
    • +1 more
    Affected versions:
    • >= 4.0.0, < 4.0.4
    • >= 3.0.0, < 3.0.2
    • < 2.3.2

    ### Impact `picomatch` is 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. Examples of problematic patterns include `+(a|aa)`, `+(*|?)`, `+(+(a))`, `*(+(a))`, and `+(+(+(a)))`. In local reproduction, these patterns caused multi-second event-loop blocking with relatively short inputs. For example, `+

    CVE: CVE-2026-33671

Showing 1-3 of 3 vulnerabilities