Skip to content

chore(deps): update dependency brace-expansion@>=1.0.0 <=1.1.11 to v2 [security]#846

Closed
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-brace-expansion-=1.0.0-=1.1.11-vulnerability
Closed

chore(deps): update dependency brace-expansion@>=1.0.0 <=1.1.11 to v2 [security]#846
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-brace-expansion-=1.0.0-=1.1.11-vulnerability

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Apr 15, 2026

This PR contains the following updates:

Package Change Age Confidence
brace-expansion@>=1.0.0 <=1.1.11 [>=1.1.12>=2.0.3](https://renovatebot.com/diffs/npm/brace-expansion@>=1.0.0 <=1.1.11/1.1.12/2.0.3) age confidence

brace-expansion: Zero-step sequence causes process hang and memory exhaustion

CVE-2026-33750 / GHSA-f886-m6hf-6m8v

More information

Details

Impact

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 for seconds and allocate heaps of memory.

The loop in question:

https://github.com/juliangruber/brace-expansion/blob/daa71bcb4a30a2df9bcb7f7b8daaf2ab30e5794a/src/index.ts#L184

test() is one of

https://github.com/juliangruber/brace-expansion/blob/daa71bcb4a30a2df9bcb7f7b8daaf2ab30e5794a/src/index.ts#L107-L113

The increment is computed as Math.abs(0) = 0, so the loop variable never advances. On a test machine, the process hangs for about 3.5 seconds and allocates roughly 1.9 GB of memory before throwing a RangeError. Setting max to any value has no effect because the limit is only checked at the output combination step, not during sequence generation.

This affects any application that passes untrusted strings to expand(), or by error sets a step value of 0. That includes tools built on minimatch/glob that resolve patterns from CLI arguments or config files. The input needed is just 10 bytes.

Patches

Upgrade to versions

  • 5.0.5+

A step increment of 0 is now sanitized to 1, which matches bash behavior.

Workarounds

Sanitize strings passed to expand() to ensure a step value of 0 is not used.

Severity

  • CVSS Score: 6.5 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


Release Notes

juliangruber/brace-expansion (brace-expansion@>=1.0.0 <=1.1.11)

v2.0.3

Compare Source

v2.0.2

Compare Source


v2.0.1

Compare Source

v2.0.0

Compare Source

v1.1.14

Compare Source

v1.1.13

Compare Source


Configuration

📅 Schedule: (in timezone America/New_York)

  • Branch creation
    • ""
  • Automerge
    • Monday through Friday (* * * * 1-5)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot enabled auto-merge (squash) April 15, 2026 17:21
@renovate renovate Bot force-pushed the renovate/npm-brace-expansion-=1.0.0-=1.1.11-vulnerability branch 2 times, most recently from 1aa3fc8 to fa8ae57 Compare April 16, 2026 07:57
@renovate renovate Bot changed the title chore(deps): update dependency brace-expansion@>=1.0.0 <=1.1.11 to >=1.1.14 [security] chore(deps): update dependency brace-expansion@>=1.0.0 <=1.1.11 to v2 [security] Apr 16, 2026
@renovate renovate Bot force-pushed the renovate/npm-brace-expansion-=1.0.0-=1.1.11-vulnerability branch from fa8ae57 to 48907ad Compare April 16, 2026 18:50
@renovate renovate Bot changed the title chore(deps): update dependency brace-expansion@>=1.0.0 <=1.1.11 to v2 [security] chore(deps): update dependency brace-expansion@>=1.0.0 <=1.1.11 to >=1.1.14 [security] Apr 17, 2026
@renovate renovate Bot force-pushed the renovate/npm-brace-expansion-=1.0.0-=1.1.11-vulnerability branch from 48907ad to cd36c17 Compare April 17, 2026 10:19
@renovate renovate Bot changed the title chore(deps): update dependency brace-expansion@>=1.0.0 <=1.1.11 to >=1.1.14 [security] chore(deps): update dependency brace-expansion@>=1.0.0 <=1.1.11 to v2 [security] Apr 17, 2026
@renovate renovate Bot force-pushed the renovate/npm-brace-expansion-=1.0.0-=1.1.11-vulnerability branch from cd36c17 to f389842 Compare April 17, 2026 10:22
@renovate renovate Bot changed the title chore(deps): update dependency brace-expansion@>=1.0.0 <=1.1.11 to v2 [security] chore(deps): update dependency brace-expansion@>=1.0.0 <=1.1.11 to >=1.1.14 [security] Apr 19, 2026
@renovate renovate Bot force-pushed the renovate/npm-brace-expansion-=1.0.0-=1.1.11-vulnerability branch from f389842 to 29d5346 Compare April 19, 2026 11:17
… [security]

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate Bot changed the title chore(deps): update dependency brace-expansion@>=1.0.0 <=1.1.11 to >=1.1.14 [security] chore(deps): update dependency brace-expansion@>=1.0.0 <=1.1.11 to v2 [security] Apr 19, 2026
@renovate renovate Bot force-pushed the renovate/npm-brace-expansion-=1.0.0-=1.1.11-vulnerability branch from 29d5346 to 260c238 Compare April 19, 2026 18:43
@vaibhavrajsingh2001
Copy link
Copy Markdown
Contributor

Closed in favor of #851

auto-merge was automatically disabled April 21, 2026 05:47

Pull request was closed

@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Apr 21, 2026

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 2.x releases. But if you manually upgrade to 2.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate Bot deleted the renovate/npm-brace-expansion-=1.0.0-=1.1.11-vulnerability branch April 21, 2026 05:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant