---
title: "GHSA-mh99-v99m-4gvg: brace-expansion: DoS via unbounded expansion length causing an out-of-memory process crash"
description: "High severity. brace-expansion: DoS via unbounded expansion length causing an out-of-memory process crash. Affects brace-expansion; fixed in 5.0.8."
url: https://inlinr.com/advisories/GHSA-mh99-v99m-4gvg
lang: en
---

[Packages](https://inlinr.com/packages) / [brace-expansion](https://inlinr.com/packages/brace-expansion) / [Security](https://inlinr.com/packages/brace-expansion/security)

High Vulnerability GHSA-mh99-v99m-4gvg CVE-2026-14257 Published 24 Jul 2026

# brace-expansion: DoS via unbounded expansion length causing an out-of-memory process crash

Your version 

Affected releases · [brace-expansion](https://inlinr.com/packages/brace-expansion)

- 5.x 5.0.2 – 5.0.7 Fixed in 5.0.8
- 4.x 4.0.0 – 4.0.1 No fix on this line yet
- 3.x 3.0.0 – 3.0.2 Fixed in 3.0.3
- 2.x 2.0.0 – 2.1.2 Fixed in 2.1.3
- 1.x 1.0.0 – 1.1.16 Fixed in 1.1.17
- 0.0.x 0.0.0 No fix on this line yet

On 5.x, the newest line:

```
npm install brace-expansion@5.0.8
```

Every release on a timeline

5.x 

1. Affected

5.0.2 – 5.0.7  
6 releases
2. Fixed

5.0.8 – 5.0.13  
6 releases, latest

4.x 

1. Affected

4.0.0 – 4.0.1  
2 releases

3.x 

1. Affected

3.0.0 – 3.0.2  
3 releases
2. Fixed

3.0.3 – 3.0.10  
8 releases

2.x 

1. Affected

2.0.0 – 2.1.2  
7 releases
2. Fixed

2.1.3 – 2.1.8  
6 releases

1.x 

1. Affected

1.0.0 – 1.1.16  
19 releases
2. Fixed

1.1.17 – 1.1.22  
6 releases

0.x 

1. Affected

0.0.0  
1 release

64 stable releases of brace-expansion, oldest to newest, one row per major.

## What happens

Summary

`expand()` bounds the _number_ of results it produces (the `max` option, `100_000` by default) but not their _length_. By chaining many brace groups, an attacker keeps the result count under `max` while making every result grow with the number of groups. Building `max` long results — plus the intermediate arrays combined at each brace group — exhausts memory and crashes the Node process with an **uncatchable** out-of-memory error. `try/catch` around `expand()` does not help: the fatal error terminates the process.

A \~7.5 KB input (`'{a,b}'.repeat(1500)`) is enough to crash a default Node process.

Details

For `N` chained brace groups such as `'{a,b}'.repeat(N)`:

- the result count is `2^N`, immediately capped at `max` (`100_000`), so the `max` protection appears to hold, but
- each result is `N` characters long, so the total output size is `max × N` characters, which grows without bound in `N`.

`expand_` combines each brace set with the fully-expanded tail:

```
const post = m.post.length ? expand_(m.post, max, false) : ['']
...
for (let j = 0; j < N.length; j++) {
  for (let k = 0; k < post.length && expansions.length < max; k++) {
    const expansion = pre + N[j] + post[k]   // grows one group longer per level
    ...
    expansions.push(expansion)
  }
}
```

The loop guard `expansions.length < max` limits how many strings are built, but nothing limits how long they get. Each recursion level materializes another array of up to `max` strings, one character longer than the level below, and — because V8 represents `pre + N[j] + post[k]` as a cons-string (rope) that references `post[k]` — those intermediate strings stay reachable through the whole chain. Memory therefore scales with `max × N`.

Measured on `5.0.7` (`'{a,b}'.repeat(N)`, default `max`):

| groups (N) | input bytes | result count | peak RSS      |
| ---------- | ----------- | ------------ | ------------- |
| 20         | 100         | 100,000      | \~80 MB       |
| 50         | 250         | 100,000      | \~214 MB      |
| 100        | 500         | 100,000      | \~409 MB      |
| 300        | 1,500       | 100,000      | \~1,148 MB    |
| 1500       | 7,500       | —            | **OOM crash** |

Proof of concept

```
const { expand } = require('brace-expansion')

// ~7.5 KB input — crashes the process with a fatal, uncatchable OOM:
//   FATAL ERROR: ... JavaScript heap out of memory
try {
  expand('{a,b}'.repeat(1500))
} catch (e) {
  // never reached — the process is already dead
}
```

Impact

Any application that passes attacker-influenced strings to `brace-expansion.expand()` — directly, or transitively via `minimatch` / `glob`brace patterns — can be crashed by a small request. Because the failure is a fatal V8 out-of-memory error rather than a thrown exception, it cannot be caught and it takes down the whole worker/process, denying service.

Remediation

Upgrade to a patched release. The fix bounds the total number of characters a single `expand()` call may accumulate (`EXPANSION_MAX_LENGTH`, default `4_000_000`, configurable via a new `maxLength` option), applied inside the output-building loops so intermediate arrays are bounded too. Once the limit is reached, output is truncated — consistent with how `max` already truncates — instead of growing without bound. The limit sits well above any realistic expansion (100,000 results hitting `max` measure \~1M characters), so legitimate input is unaffected.

After the fix, `'{a,b}'.repeat(1500)` returns a bounded, truncated result in \~0.7 s using \~340 MB and never crashes, including under a constrained 512 MB heap.

The fix bounds memory but the algorithm still rebuilds intermediate arrays at each level (roughly `O(N × maxLength)` work on this input class). A streaming rewrite that produces output in `O(total output size)` can be a non-urgent follow-up.

If immediate upgrade isn't possible, avoid passing untrusted input to `expand()` / glob brace patterns, or pass a small explicit `max` **and** `maxLength`.

## How it is exploited

Exploitable over the network, with no account and no action from a user.

- **Confidentiality**: none
- **Integrity**: none
- **Availability**: high

CVSS:3.1/​AV:N/​AC:L/​PR:N/​UI:N/​S:U/​C:N/​I:N/​A:H

## References

- [Reference](https://github.com/juliangruber/brace-expansion/security/advisories/GHSA-mh99-v99m-4gvg "https://github.com/juliangruber/brace-expansion/security/advisories/GHSA-mh99-v99m-4gvg")  
github.com/juliangruber/brace-expansion/securit…
- [NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-14257 "https://nvd.nist.gov/vuln/detail/CVE-2026-14257")  
nvd.nist.gov/vuln/detail/CVE-2026-14257
- [Pull request](https://github.com/juliangruber/brace-expansion/pull/129 "https://github.com/juliangruber/brace-expansion/pull/129")  
#129
- [Pull request](https://github.com/juliangruber/brace-expansion/pull/130 "https://github.com/juliangruber/brace-expansion/pull/130")  
#130
- [Pull request](https://github.com/juliangruber/brace-expansion/pull/136 "https://github.com/juliangruber/brace-expansion/pull/136")  
#136
- [Fix commit](https://github.com/juliangruber/brace-expansion/commit/139d015104e71433ad52a41d19467c48ecbb2c7d "https://github.com/juliangruber/brace-expansion/commit/139d015104e71433ad52a41d19467c48ecbb2c7d")  
139d015
- [Fix commit](https://github.com/juliangruber/brace-expansion/commit/a1bd33999ea75262c4749fff3bbb0d1372bd07b5 "https://github.com/juliangruber/brace-expansion/commit/a1bd33999ea75262c4749fff3bbb0d1372bd07b5")  
a1bd339
- [Fix commit](https://github.com/juliangruber/brace-expansion/commit/cb4b9e47cc2ec777c14b2b4492fb431a56f6a031 "https://github.com/juliangruber/brace-expansion/commit/cb4b9e47cc2ec777c14b2b4492fb431a56f6a031")  
cb4b9e4
- [Fix commit](https://github.com/juliangruber/brace-expansion/commit/d13ff455a58b0d56704f0111e3c2a0b16ceb06eb "https://github.com/juliangruber/brace-expansion/commit/d13ff455a58b0d56704f0111e3c2a0b16ceb06eb")  
d13ff45
- [Package](https://github.com/juliangruber/brace-expansion "https://github.com/juliangruber/brace-expansion")  
github.com/juliangruber/brace-expansion
- [Reference](https://www.npmjs.com/package/brace-expansion "https://www.npmjs.com/package/brace-expansion")  
npmjs.com/package/brace-expansion

A whole project to check? Paste its package.json in the [dependency check](https://inlinr.com/tools/dependency-check): every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.
