[lexical] Chore: Fix path-to-regexp dependency vulnerability#8415
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
meta-cla
Bot
added
the
CLA Signed
vishisht31
requested review from
acywatson,
etrepum,
fantactuka,
ivailop7,
potatowagon,
takuyakanbr and
zurfyx
as code owners
etrepum
approved these changes
Apr 28, 2026
etrepum
pushed a commit
to etrepum/lexical
that referenced
this pull request
May 2, 2026
Audited every override against the current dep tree by removing it and re-resolving. The CVE-style overrides that survived the last few audit PRs (facebook#8380, facebook#8399, facebook#8401, facebook#8404-facebook#8409, facebook#8415) are no longer doing any work — every consumer either pins or ranges its way to a patched release without help: qs 6.15.0 -> 6.14.2 (override threshold met) simple-git 3.36.0 -> 3.36.0 (no change) follow-redirects 1.16.0 -> 1.16.0 (no change) protobufjs 8.0.1 -> 7.5.6 (>=7.5.5 patched) dompurify 3.4.1 -> 3.4.1 (no change) postcss 8.5.13 -> 8.5.13 (no change) eslint 10.2+10.3 -> 10.3.0 (override was forcing dup) immutable 4.3.8 -> 4.3.8 (no change) path-to-regexp 1.x 1.9.0 -> 1.9.0 (no change; ^1.7.0 only matches 1.9.0 anyway) form-data, @isaacs/brace-expansion, astro: not in tree at all. uuid drops from 14.0.0 to 11.1.1 + a transitive 8.3.2; the 8.3.2 path predates the GHSA-pwhh-q4h6-w599 fix but the consumer doesn't use the v3/v5 entrypoints, and forcing 14.0.0 on consumers ranged at ^8 was the same kind of major-jumping mistake that just broke react-router with path-to-regexp 8.x. Kept the deduplicating pins (react, react-dom, @types/node, prettier) and the version-scoped yaml@^1 override, which is also defensive but correctly range-bounded.
Merged
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
2 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.
Description
Updated package.json to manually override the version of the dependency path-to-regexp to >=0.1.13 to address the security vulnerability.
Repository: facebook/lexical
Manifest file: pnpm-lock.yaml
Package name: path-to-regexp
Affected versions: < 0.1.13
Fixed in version: 0.1.13
Test plan
Before
N/A
After
N/A