fix(repo): bump picomatch from 4.0.2 to 4.0.4#35081
Merged
Merged
Conversation
## Current Behavior picomatch 4.0.2 has two known high-severity vulnerabilities: - GHSA-3v7f-55p6-f55p (Method Injection in POSIX Character Classes) - GHSA-c2c7-rcm5-vvqj (ReDoS via extglob quantifiers) This causes `npm audit` to flag @nx/angular, @nx/js, @nx/workspace, and other packages that depend on picomatch. ## Expected Behavior No picomatch-related vulnerabilities reported by `npm audit`. ## Related Issue(s) Fixes #35068
✅ Deploy Preview for nx-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for nx-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
|
View your CI Pipeline Execution ↗ for commit 6949b69
☁️ Nx Cloud last updated this comment at |
FrozenPandaz
approved these changes
Mar 30, 2026
AgentEnder
approved these changes
Mar 30, 2026
FrozenPandaz
pushed a commit
that referenced
this pull request
Mar 31, 2026
## Current Behavior The pnpm catalog pins picomatch to `4.0.2`, which has two high-severity vulnerabilities: - [GHSA-3v7f-55p6-f55p](GHSA-3v7f-55p6-f55p) — Method Injection in POSIX Character Classes causes incorrect glob matching - [GHSA-c2c7-rcm5-vvqj](GHSA-c2c7-rcm5-vvqj) — ReDoS via extglob quantifiers Running `npm audit` on any workspace using `@nx/angular`, `@nx/js`, or `@nx/workspace` reports these vulnerabilities. ## Expected Behavior No picomatch-related vulnerabilities reported by `npm audit`. The bump to `4.0.4` is a patch release that only fixes the security issues with no API changes. ## Related Issue(s) Fixes #35068 (cherry picked from commit 203203f)
Contributor
|
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Current Behavior
The pnpm catalog pins picomatch to
4.0.2, which has two high-severity vulnerabilities:Running
npm auditon any workspace using@nx/angular,@nx/js, or@nx/workspacereports these vulnerabilities.Expected Behavior
No picomatch-related vulnerabilities reported by
npm audit. The bump to4.0.4is a patch release that only fixes the security issues with no API changes.Related Issue(s)
Fixes #35068