CVE-2026-13149: brace-expansion: DoS via exponential-time expansion of consecutive non-expanding {} groups
High CVSS 5.3
- OSV id
- GHSA-3jxr-9vmj-r5cp
- Also known as
- CVE-2026-13149
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| brace-expansion npm |
>= 3.0.0, < 5.0.7 | 5.0.7 |
| brace-expansion npm |
< 1.1.16 | 1.1.16 |
| brace-expansion npm |
>= 2.0.0, < 2.1.2 | 2.1.2 |
Versions we track that it affects: 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.7 or later.
npm install brace-expansion@5.0.7
# 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.16 or later.
npm install brace-expansion@1.1.16
# 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.1.2 or later.
npm install brace-expansion@2.1.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.
Not sure whether your project uses an affected version? Check your lockfile below for free.
Details
Summary
brace-expansion's expand() exhibits exponential-time - O(2ⁿ) - behavior in the number of consecutive non-expanding {} groups. A short, all-ASCII input (~90 bytes/30 groups) blocks the calling thread for minutes; a slightly longer input hangs it effectively indefinitely. Because the dominant consumers run on Node's single-threaded event loop, one small input can fully stall a worker/process.
In expand_, post is computed unconditionally at the top of the function, before the early-return branches that don't use it:
const post = m.post.length ? expand_(m.post, max, false) : ['']; // always recurses
...
if (!isSequence && !isOptions) {
if (m.post.match(/,(?!,).*\}/)) {
str = m.pre + '{' + m.body + escClose + m.post;
return expand_(str, max, true); // restart — `post` discarded
}
return [str];
}
For input like a{},{},…, the first {} is non-expanding, so control reaches the {a},b} rewrite branch - but expand_ has already recursed into post over the entire remaining tail, only to throw the result away.
Each level therefore spawns two recursive expansions over essentially the same remaining work: T(n) = 2·T(n−1) ⇒ O(2ⁿ).
The max option does not mitigate this: max only bounds the output-building loops; neither the post recursion nor the rewrite recursion consults it.
Measured on 5.0.6:
| groups (n) | input bytes | time |
|---|---|---|
| 20 | 60 | 130 ms |
| 24 | 72 | 1.9 s |
| 26 | 78 | 7.8 s |
| 30 (PoC) | 90 | ~2 min |
Proof of concept
const { expand } = require('brace-expansion');
// 30 non-expanding groups, ~90 bytes — blocks for minutes:
expand('a{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{}');
Impact
Any application that passes attacker-influenced strings to brace-expansion.expand() - directly or transitively via minimatch/glob brace patterns - can be driven into a multi-minute-to-indefinite CPU hang by a tiny request, denying service on that thread/process.
Remediation
Upgrade to a patched release. The fix:
- Defers computing post until after the early-return branches (and computes it locally in the $-suffix branch), so post is only expanded when a brace set actually expands and the value is used. This alone removes the exponential.
- Converts the {a},b} rewrite from recursion to an in-function loop, so a long run of rewrites cannot grow the call stack.
Verified: the PoC drops from ~2 min to 0.55 ms, 5,000 groups complete in ~344 ms, and output is identical to 5.0.6 across a behavioral-equivalence suite (sequences, padding, $-prefix, a{},b}c, {},a}b, x{{a,b}}y, etc.). Post-fix complexity is ~O(n²) on this input class - acceptable for the security fix; a linear rewrite can be a non-urgent follow-up.
If immediate upgrade isn't possible, avoid passing untrusted input to expand() / glob brace patterns, or run such expansion under a timeout/worker.
References
- GHSA-3jxr-9vmj-r5cp on OSV.dev
- Web: https://github.com/juliangruber/brace-expansion/security/advisories/GHSA-3jxr-9vmj-r5cp
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-13149
- Web: https://github.com/juliangruber/brace-expansion/pull/122
- Web: https://github.com/juliangruber/brace-expansion/pull/123
- Web: https://github.com/juliangruber/brace-expansion/commit/835d6be91201122d9adffb0c0c8c094189ace265
- Web: https://github.com/juliangruber/brace-expansion/commit/c7e33ec13ac1a684c116720843ce24e208611754
- Web: https://github.com/juliangruber/brace-expansion/commit/d74e63030c012e3b7ae81657b8d665619cd51b95
- Package: https://github.com/juliangruber/brace-expansion
- Web: https://github.com/juliangruber/brace-expansion/releases/tag/v1.1.16
- Web: https://github.com/juliangruber/brace-expansion/releases/tag/v2.1.2
- Web: https://github.com/juliangruber/brace-expansion/releases/tag/v5.0.7
- Web: https://www.npmjs.com/package/brace-expansion
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.