Update dependency picomatch to v4.0.4 [SECURITY]#24
Open
balena-renovate[bot] wants to merge 1 commit intomainfrom
Open
Update dependency picomatch to v4.0.4 [SECURITY]#24balena-renovate[bot] wants to merge 1 commit intomainfrom
balena-renovate[bot] wants to merge 1 commit intomainfrom
Conversation
Update picomatch from 4.0.3 to 4.0.4 Change-type: patch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.0.3→4.0.4Picomatch: Method Injection in POSIX Character Classes causes incorrect Glob Matching
CVE-2026-33672 / GHSA-3v7f-55p6-f55p
More information
Details
Impact
picomatch is vulnerable to a method injection vulnerability (CWE-1321) affecting the
POSIX_REGEX_SOURCEobject. Because the object inherits fromObject.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
picomatchversions 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:Resources
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
micromatch/picomatch (picomatch)
v4.0.4Compare Source
This is a security release fixing several security relevant issues.
What's Changed
Full Changelog: micromatch/picomatch@4.0.3...4.0.4
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate.