Advisory

GHSA-f886-m6hf-6m8v

Also known as: CVE-2026-33750

Summary

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

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

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-03-26 18:29 UTC
Modified
2026-09-10 03:51 UTC

Affected packages and fixes

brace-expansion

npm · All systems

Affected

  • introduced 4.0.0, fixed 5.0.5 (semver)

Fixed versions

5.0.5

Fix

brace-expansion

npm · All systems

Affected

  • introduced 3.0.0, fixed 3.0.2 (semver)

Fixed versions

3.0.2

Fix

brace-expansion

npm · All systems

Affected

  • introduced 2.0.0, fixed 2.0.3 (semver)

Fixed versions

2.0.3

Fix

brace-expansion

npm · All systems

Affected

  • introduced 0, fixed 1.1.13 (semver)

Fixed versions

1.1.13

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences