---
title: "GHSA-jxxr-4gwj-5jf2: brace-expansion: Large numeric range defeats documented `max` DoS protection"
description: "Moderate severity. brace-expansion: Large numeric range defeats documented `max` DoS protection. Affects brace-expansion; fixed in 5.0.6."
url: https://inlinr.com/advisories/GHSA-jxxr-4gwj-5jf2
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-jxxr-4gwj-5jf2 CVE-2026-45149 Published 18 May 2026

# brace-expansion: Large numeric range defeats documented \`max\` DoS protection

Your version 

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

- 5.x 5.0.2 – 5.0.5 Fixed in 5.0.6

On 5.x, the newest line:

```
npm install brace-expansion@5.0.6
```

Every release on a timeline

1. Not affected

0.0.0 – 4.0.1  
52 releases
2. Affected

5.0.2 – 5.0.5  
4 releases
3. Fixed

5.0.6 – 5.0.13  
8 releases, latest

64 stable releases of brace-expansion, oldest to newest.

## What happens

The `max` option was being applied too late:

When expanding a single large numeric range like `{1..10000000}`, the sequence generation loop generates all 10 million intermediate elements before the `max` limit is applied With `max=10`, the output is correctly limited to 10 items, but the process still allocates `~505 MB` and spends `~800ms` building the full intermediate array.

Workaround

Ensure the string to be expanded doesn't contain more values than the desired `max` item count.

## How it is exploited

Exploitable over the network, with no account and a user to do something.

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

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

## References

- [Reference](https://github.com/juliangruber/brace-expansion/security/advisories/GHSA-jxxr-4gwj-5jf2 "https://github.com/juliangruber/brace-expansion/security/advisories/GHSA-jxxr-4gwj-5jf2")  
github.com/juliangruber/brace-expansion/securit…
- [NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-45149 "https://nvd.nist.gov/vuln/detail/CVE-2026-45149")  
nvd.nist.gov/vuln/detail/CVE-2026-45149
- [Fix commit](https://github.com/juliangruber/brace-expansion/commit/c0b095bdc52bc4c36dc88deddbadabc49f8371e5 "https://github.com/juliangruber/brace-expansion/commit/c0b095bdc52bc4c36dc88deddbadabc49f8371e5")  
c0b095b
- [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.
