CVE-2026-33750: brace-expansion: Zero-step sequence causes process hang and memory exhaustion
Medium CVSS 6.5
- OSV id
- GHSA-f886-m6hf-6m8v
- Also known as
- CVE-2026-33750
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| brace-expansion npm |
>= 4.0.0, < 5.0.5 | 5.0.5 |
| brace-expansion npm |
>= 3.0.0, < 3.0.2 | 3.0.2 |
| brace-expansion npm |
>= 2.0.0, < 2.0.3 | 2.0.3 |
| brace-expansion npm |
< 1.1.13 | 1.1.13 |
Versions we track that it affects: brace-expansion 2.0.1; brace-expansion 2.0.1; brace-expansion 2.0.1; brace-expansion 2.0.1
How to fix it
brace-expansion (npm)
Upgrade brace-expansion to 5.0.5 or later.
npm install brace-expansion@5.0.5
# if it is an indirect dependency: npm update brace-expansion (or npm audit fix)
- If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
- Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
brace-expansion (npm)
Upgrade brace-expansion to 3.0.2 or later.
npm install brace-expansion@3.0.2
# if it is an indirect dependency: npm update brace-expansion (or npm audit fix)
- If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
- Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
brace-expansion (npm)
Upgrade brace-expansion to 2.0.3 or later.
npm install brace-expansion@2.0.3
# if it is an indirect dependency: npm update brace-expansion (or npm audit fix)
- If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
- Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
brace-expansion (npm)
Upgrade brace-expansion to 1.1.13 or later.
npm install brace-expansion@1.1.13
# if it is an indirect dependency: npm update brace-expansion (or npm audit fix)
- If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
- Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
Not sure whether your project uses an affected version? Check your lockfile below for free.
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.
References
- GHSA-f886-m6hf-6m8v on OSV.dev
- Web: https://github.com/juliangruber/brace-expansion/security/advisories/GHSA-f886-m6hf-6m8v
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-33750
- Web: https://github.com/juliangruber/brace-expansion/issues/98
- Web: https://github.com/juliangruber/brace-expansion/pull/95
- Web: https://github.com/juliangruber/brace-expansion/pull/96
- Web: https://github.com/juliangruber/brace-expansion/pull/97
- Web: https://github.com/juliangruber/brace-expansion/commit/311ac0d54994158c0a384e286a7d6cbb17ee8ed5
- Web: https://github.com/juliangruber/brace-expansion/commit/7fd684f89fdde3549563d0a6522226a9189472a2
- Web: https://github.com/juliangruber/brace-expansion/commit/b9cacd9e55e7a1fa588fe4b7bb1159d52f1d902a
- Package: https://github.com/juliangruber/brace-expansion
- Web: https://github.com/juliangruber/brace-expansion/blob/daa71bcb4a30a2df9bcb7f7b8daaf2ab30e5794a/src/index.ts#L107-L113
- Web: https://github.com/juliangruber/brace-expansion/blob/daa71bcb4a30a2df9bcb7f7b8daaf2ab30e5794a/src/index.ts#L184
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.