p PatchFirst

CVE-2026-33672

CVE-2026-33672 · Picomatch: Method Injection in POSIX Character Classes causes incorrect Glob Matching

This page contains facts from public vulnerability sources. Check the original advisory before updating.

Picomatch is a glob matcher written JavaScript. Versions prior to 4.0.4, 3.0.2, and 2.3.2 are vulnerable to a method injection vulnerability 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. 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 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; and manually patching the library by modifying `POSIX_REGEX_SOURCE` to use a null prototype.

CVSS 5.3 · Medium · EPSS 0.6% · Fix available

Published
Updated

Stack: system · node

Affected products and versions

  • picomatch

    Versions
    • >= 4.0.0, < 4.0.4: Affected
    • >= 3.0.0, < 3.0.2: Affected
    • < 2.3.2: Affected

    No fix published

  • node-anymatch Debian:12

    Versions
    • 3.1.3+~cs4.6.1-2
    • 3.1.3+~cs8.0.5-1
    • 3.1.3+~cs8.0.6-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • node-anymatch Debian:13

    Versions
    • 3.1.3+~cs4.6.1-2
    • 3.1.3+~cs8.0.5-1
    • 3.1.3+~cs8.0.6-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • node-anymatch Debian:14

    Versions
    • 3.1.3+~cs4.6.1-2
    • 3.1.3+~cs8.0.5-1
    Affected ranges
    • ECOSYSTEM: < 3.1.3+~cs8.0.6-1

    Update to 3.1.3+~cs8.0.6-1

  • picomatch npm

    Affected ranges
    • SEMVER: ≥ 4.0.0, < 4.0.4

    Update to 4.0.4

  • picomatch npm

    Affected ranges
    • SEMVER: ≥ 3.0.0, < 3.0.2

    Update to 3.0.2

  • picomatch npm

    Affected ranges
    • SEMVER: < 2.3.2

    Update to 2.3.2

  • node-anymatch Ubuntu:18.04:LTS

    Versions
    • 1.3.0-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • node-anymatch Ubuntu:20.04:LTS

    Versions
    • 3.0.3+~2.0.7-3
    • 3.1.1+~2.1.1-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • node-anymatch Ubuntu:22.04:LTS

    Versions
    • 3.1.1+~2.2.2-1
    • 3.1.2+~cs4.5.6-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • node-anymatch Ubuntu:24.04:LTS

    Versions
    • 3.1.3+~cs4.6.1-2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • node-anymatch Ubuntu:25.10

    Versions
    • 3.1.3+~cs4.6.1-2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • node-anymatch Ubuntu:26.04:LTS

    Versions
    • 3.1.3+~cs4.6.1-2
    • 3.1.3+~cs8.0.6-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

Original sources

Check your server →