CVE-2026-33750: brace-expansion: Zero-step sequence causes process hang and memory exhaustion
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.
Other sources
brace-expansion: Zero-step sequence causes process hang and memory exhaustion
— Microsoft
The brace-expansion library generates arbitrary strings containing a common prefix and suffix. Prior to versions 5.0.5, 3.0.2, 2.0.3, and 1.1.13, 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. Versions 5.0.5, 3.0.2, 2.0.3, and 1.1.13 fix the issue. As a workaround, sanitize strings passed to expand() to ensure a step value of 0 is not used.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/brace-expansionto a version that resolves this vulnerability.Fixed in 1.1.13 - Upgrade
Upgrade
npm/brace-expansionto a version that resolves this vulnerability.Fixed in 2.0.3 - Upgrade
Upgrade
npm/brace-expansionto a version that resolves this vulnerability.Fixed in 3.0.2 - Upgrade
Upgrade
npm/brace-expansionto a version that resolves this vulnerability.Fixed in 5.0.5 - Upgrade
Upgrade
brace-expansionto a version that resolves this vulnerability.Fixed in 5.0.5 - Upgrade
Upgrade
brace-expansionto a version that resolves this vulnerability.Fixed in 3.0.2 - Upgrade
Upgrade
brace-expansionto a version that resolves this vulnerability.Fixed in 2.0.3 - Upgrade
Upgrade
brace-expansionto a version that resolves this vulnerability.Fixed in 1.1.13 - Configuration
As a workaround, sanitize strings passed to `expand()` so a step value of `0` is not used (0 should be converted to `1`).
brace-expansion (expand function) brace pattern zero step value = sanitize step value so 0 is not used (treat 0 as 1)
Event History
Frequently Asked Questions
What is the severity of CVE-2026-33750?
CVE-2026-33750 is assigned a high severity due to its potential to cause applications to hang indefinitely and exhaust system memory.
How do I fix CVE-2026-33750?
To fix CVE-2026-33750, upgrade the brace-expansion package to versions greater than 5.0.5.
What causes the vulnerability CVE-2026-33750?
CVE-2026-33750 is caused by a brace pattern with a zero step value, leading to an infinite loop during sequence generation.
Who is affected by CVE-2026-33750?
Users of the brace-expansion package version 5.0.5 and below are affected by CVE-2026-33750.
Is CVE-2026-33750 a code execution vulnerability?
CVE-2026-33750 is not a code execution vulnerability, but rather a resource exhaustion issue that leads to unresponsive applications.