chore(deps): update dependency picomatch to v4.0.4 [security]#523
Open
renovate[bot] wants to merge 1 commit intomainfrom
Open
chore(deps): update dependency picomatch to v4.0.4 [security]#523renovate[bot] wants to merge 1 commit intomainfrom
renovate[bot] wants to merge 1 commit intomainfrom
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.1→4.0.4GitHub Vulnerability Alerts
CVE-2026-33671
Impact
picomatchis 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,+(a|aa)compiled to^(?:(?=.)(?:a|aa)+)$and took about 2 seconds to reject a 41-character non-matching input, while nested patterns such as+(+(a))and*(+(a))took around 29 seconds to reject a 33-character input on a modern M1 MacBook.Applications are impacted when they allow untrusted users to supply glob patterns that are passed to
picomatchfor 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.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:
noextglob: true+()and*()Resources
lib/parse.jsandlib/constants.jsare involved in generating the vulnerable regex formsmicromatch)path-to-regexp)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
v4.0.3Compare Source
v4.0.2Compare Source
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.