---
title: "GHSA-q2hr-2g5m-vwhr: brace-expansion: Quadratic-time expansion of the `{a},b}` rewrite causes CPU denial of service"
description: "Moderate severity. brace-expansion: Quadratic-time expansion of the `{a},b}` rewrite causes CPU denial of service. Affects brace-expansion; fixed in 5.0.12."
url: https://inlinr.com/advisories/GHSA-q2hr-2g5m-vwhr
lang: en
---

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

Moderate Vulnerability GHSA-q2hr-2g5m-vwhr CVE-2026-102277 Published 29 Sep 2026

# brace-expansion: Quadratic-time expansion of the \`{a},b}\` rewrite causes CPU denial of service

Your version 

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

- 5.x 5.0.2 – 5.0.11 Fixed in 5.0.12
- 4.x 4.0.0 – 4.0.1 No fix on this line yet
- 3.x 3.0.0 – 3.0.8 Fixed in 3.0.9
- 2.x 2.0.0 – 2.1.6 Fixed in 2.1.7
- 1.x 1.0.0 – 1.1.20 Fixed in 1.1.21
- 0.0.x 0.0.0 No fix on this line yet

On 5.x, the newest line:

```
npm install brace-expansion@5.0.12
```

Every release on a timeline

5.x 

1. Affected

5.0.2 – 5.0.11  
10 releases
2. Fixed

5.0.12 – 5.0.13  
2 releases, latest

4.x 

1. Affected

4.0.0 – 4.0.1  
2 releases

3.x 

1. Affected

3.0.0 – 3.0.8  
9 releases
2. Fixed

3.0.9 – 3.0.10  
2 releases

2.x 

1. Affected

2.0.0 – 2.1.6  
11 releases
2. Fixed

2.1.7 – 2.1.8  
2 releases

1.x 

1. Affected

1.0.0 – 1.1.20  
23 releases
2. Fixed

1.1.21 – 1.1.22  
2 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

Expanding `{a},b}`\-shaped input takes time quadratic in the number of literal `}` characters, blocking the event loop.

Bash preserves a quirk where a brace group followed by a comma set still expands (`{a},b}`). The parser implements this by rewriting the string and restarting the scan. Each pass absorbs exactly one `}` and re-scans from the beginning, so `n` trailing braces cost `n` full passes.

Reproduction

```
const build = n => '{a}' + '}'.repeat(n) + ',z}'

for (const n of [8000, 16000, 32000, 64000, 128000]) {
  const t = Date.now()
  expand(build(n))
  console.log(n, Date.now() - t + 'ms')
}
```

| n       | input  | time       | results |
| ------- | ------ | ---------- | ------- |
| 8,000   | 8 KB   | 110 ms     | 2       |
| 16,000  | 16 KB  | 446 ms     | 2       |
| 32,000  | 32 KB  | 1.7 s      | 2       |
| 64,000  | 64 KB  | 6.9 s      | 2       |
| 128,000 | 128 KB | **27.7 s** | 2       |

`ms/n^2` is flat at \~1.7 and each doubling of `n` costs exactly 4.0x - quadratic. 128 KB of input blocks the event loop for nearly half a minute to produce two results.

Mechanism

Instrumenting the rewrite branch confirms it runs exactly `n + 1` times, once per literal `}`, each re-scanning the whole string.

There is a second multiplier. The rewrite replaces the group's closing `}` with the internal `escClose` sentinel, which is `'\0CLOSE' + Math.random() + '\0'` \- about 25 characters. The working string therefore _grows_ by \~25 characters on every pass:

| n     | input length | final string length |
| ----- | ------------ | ------------------- |
| 1,000 | 1,006        | 26,006              |
| 8,000 | 8,006        | 208,006             |

So the input is inflated roughly 26x, and that factor multiplies both the quadratic constant and peak memory. This makes it partly a memory-pressure issue as well as a CPU one.

Why `max` and `maxLength` do not help

The cost is in parsing, before the result set exists. The payload yields 2 results regardless of size, so neither bound is ever reached.

Impact

An application passing an untrusted pattern to `expand()`, directly or through `minimatch` / `glob`, can have its event loop blocked for tens of seconds by a payload well under minimatch's 65,536-character cap. For a single-threaded Node server that is a full stall, not just a slow request.

Degraded availability rather than a crash - the process recovers once the expansion completes.

Affected versions

Verified affected on 1.1.18, 2.1.4, 3.0.6 and 5.0.9, all within a few percent of each other (\~460-490 ms at n=16,000).

Patch

The rewrite loop gets an iteration bound. Past the cap the remaining string is treated as non-expanding and returned literally, consistent with the existing `max` / `maxLength` caps, which truncate rather than throw.

Note this bounds the number of passes, not the cost of each: worst-case work remains proportional to `cap x input length`. The cap is set low enough that the residual is bounded in practice, and far above what any realistic `{a},b}` input needs.

Severity note

Scored 5.3 Medium (`A:L`) for consistency with GHSA-3jxr-9vmj-r5cp, the other algorithmic-complexity advisory on this package (CWE-407), which uses the same vector. The stack-exhaustion advisories on this package score `A:H` because they crash the process outright; this one stalls it.

## How it is exploited

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

- **Confidentiality**: none
- **Integrity**: none
- **Availability**: low

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

## References

- [Reference](https://github.com/juliangruber/brace-expansion/security/advisories/GHSA-q2hr-2g5m-vwhr "https://github.com/juliangruber/brace-expansion/security/advisories/GHSA-q2hr-2g5m-vwhr")  
github.com/juliangruber/brace-expansion/securit…
- [NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-102277 "https://nvd.nist.gov/vuln/detail/CVE-2026-102277")  
nvd.nist.gov/vuln/detail/CVE-2026-102277
- [Fix commit](https://github.com/juliangruber/brace-expansion/commit/33a5ef17b8d800bbfa8c52b14c39043b6aac1a96 "https://github.com/juliangruber/brace-expansion/commit/33a5ef17b8d800bbfa8c52b14c39043b6aac1a96")  
33a5ef1
- [Fix commit](https://github.com/juliangruber/brace-expansion/commit/bdff773f98e5988616b7039cc9b508df5d640b22 "https://github.com/juliangruber/brace-expansion/commit/bdff773f98e5988616b7039cc9b508df5d640b22")  
bdff773
- [Fix commit](https://github.com/juliangruber/brace-expansion/commit/c55e67d8d8b1c56a2474afff15c2891166b2d364 "https://github.com/juliangruber/brace-expansion/commit/c55e67d8d8b1c56a2474afff15c2891166b2d364")  
c55e67d
- [Fix commit](https://github.com/juliangruber/brace-expansion/commit/ffdfa3e3806bed17c0874b8f1439b084de354a7e "https://github.com/juliangruber/brace-expansion/commit/ffdfa3e3806bed17c0874b8f1439b084de354a7e")  
ffdfa3e
- [Package](https://github.com/juliangruber/brace-expansion "https://github.com/juliangruber/brace-expansion")  
github.com/juliangruber/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.
