fix: baseline unfixable brace-expansion dev advisory blocking self-scan#897
Merged
Conversation
…4gvg) A new brace-expansion DoS advisory (published 2026-07-24) matches two transitive dev dependencies (jest and ts-jest chains), failing self-scan on every PR. The only fix is brace-expansion >= 5.0.8 (5.x rewrite, no backport); no within-range update reaches it and, verified via the CLI's own scan, upgrading the parents (jest@30.4.2) does not resolve the transitive chain. Accept both findings via the ratcheting baseline per our fix-order policy; new findings above baseline still fail. Closes #895
This was referenced Jul 26, 2026
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
1 participant
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.
A new advisory GHSA-mh99-v99m-4gvg (brace-expansion DoS, published 2026-07-24) matches two transitive dev dependencies in our lockfile (via the
jestandts-jestchains), soself-scan(--fail-on high) now fails on every PR.The only non-vulnerable brace-expansion is
>= 5.0.8(coordinated 5.x rewrite, no backport to 1.x/2.x). A within-range update can't reach it, and - verified by running the CLI's own recommendation (npm install -D jest@30.4.2) and rescanning - the parent upgrade does not resolve the chain (glob@10.5.0still pins the vulnerableminimatch@9.0.9).Per our fix-order policy (within-range -> parent upgrade -> ratcheting baseline for a genuinely unfixable transitive dev finding, before overrides), this accepts both findings via
.cve-lite/baseline.json. Self-scan now suppresses these two known findings and passes; any new finding above baseline still fails. To be dropped onceglob/minimatch/test-excludeadopt brace-expansion 5.x.Closes #895