GHSA-3v7f-55p6-f55p Picomatch: Method Injection in POSIX Character Classes causes incorrect Glob Matching

• npm picomatch: >= 4.0.0, < 4.0.4 → fixed in 4.0.4 • npm picomatch: >= 3.0.0, < 3.0.2 → fixed in 3.0.2 • npm picomatch: < 2.3.2 → fixed in 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 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_SOURCE` to use a null prototype: ```js const POSIX_REGEX_SOURCE = { __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