Fix brace-expansion vulnerability in mocha dependency - #1857
Merged
Conversation
wenyt (wenytang-ms)
approved these changes
Apr 14, 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
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.
Summary
Fix a vulnerability in
brace-expansion(transitive dependency viamocha -> minimatch -> brace-expansion@2.0.2).Vulnerability
A brace pattern with a zero step value (e.g.,
{1..2..0}) causes the sequence generation loop to run indefinitely, making the process hang and allocate ~1.9 GB of memory before throwing aRangeError. This affects any application that passes untrusted strings toexpand().Fix
Added
brace-expansionoverride undermochainpackage.jsonto force resolution to>=2.0.3, which sanitizes a step increment of 0 to 1 (matching bash behavior). The resolved version is now5.0.5.