CVE-2026-102276: brace-expansion: DoS via uncontrolled recursion in parseCommaParts causing stack exhaustion

Published Sep 28, 2026
·
Updated

The brace-expansion library generates arbitrary strings containing a common prefix and suffix. Prior to 1.1.19, 2.1.5, 3.0.7, and 5.0.10, crafted brace patterns can exhaust the native stack in parseCommaParts because parseCommaParts recursively processes the remainder once per brace group and uses push.apply to pass every element of a very large comma-part array as a function argument. Patterns containing many comma-separated brace groups trigger the recursive path, while the large array triggers the argument-array path without deep recursion. These paths cause recursive and argument-array native stack exhaustion before max or maxLength can limit output, potentially terminating the Node.js process in a process-terminating denial of service. This issue is fixed in versions 1.1.19, 2.1.5, 3.0.7, and 5.0.10.

Affected Software

1 affected component
npm/brace-expansion<1.1.19, <2.1.5, <3.0.7, <5.0.10

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade brace-expansion to a version that resolves this vulnerability.

    Fixed in 1.1.19
  2. Upgrade

    Upgrade brace-expansion to a version that resolves this vulnerability.

    Fixed in 2.1.5
  3. Upgrade

    Upgrade brace-expansion to a version that resolves this vulnerability.

    Fixed in 3.0.7
  4. Upgrade

    Upgrade brace-expansion to a version that resolves this vulnerability.

    Fixed in 5.0.10

Event History

Sep 28, 2026
CVE Published
via MITRE·08:50 PM
Data Sourced
via MITRE·08:50 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are realistically exposed to this denial of service?

Node.js applications are exposed when they process attacker-controlled brace-expansion patterns. Exploitation can terminate the Node.js process, so services that accept patterns through network requests or other untrusted inputs are particularly relevant.

2

Does limiting expansion output with max or maxLength prevent exploitation?

No. The native stack exhaustion occurs in parseCommaParts before max or maxLength can limit the generated output.

3

What input characteristics trigger the vulnerable paths?

Patterns with many comma-separated brace groups trigger recursive processing of the remaining pattern. A very large comma-part array can also exhaust the native stack through push.apply, even without deep recursion.

4

Which versions contain the fix?

The fixed releases are 1.1.19, 2.1.5, 3.0.7, and 5.0.10. Versions before the corresponding fixed release are affected.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203