CVE-2026-25547
Unknown Unknown - Not Provided
Denial of Service in @isaacs/brace-expansion via Unbounded Brace Expansion

Publication date: 2026-02-04

Last updated on: 2026-02-04

Assigner: GitHub, Inc.

Description
@isaacs/brace-expansion is a hybrid CJS/ESM TypeScript fork of brace-expansion. Prior to version 5.0.1, @isaacs/brace-expansion is vulnerable to a denial of service (DoS) issue caused by unbounded brace range expansion. When an attacker provides a pattern containing repeated numeric brace ranges, the library attempts to eagerly generate every possible combination synchronously. Because the expansion grows exponentially, even a small input can consume excessive CPU and memory and may crash the Node.js process. This issue has been patched in version 5.0.1.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-04
Last Modified
2026-02-04
Generated
2026-05-07
AI Q&A
2026-02-05
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
isaacs brace-expansion to 5.0.1 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-1333 The product uses a regular expression with an inefficient, possibly exponential worst-case computational complexity that consumes excessive CPU cycles.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

The vulnerability exists in the @isaacs/brace-expansion library prior to version 5.0.1. It is a denial of service (DoS) issue caused by unbounded brace range expansion. When an attacker provides a pattern with repeated numeric brace ranges, the library tries to generate every possible combination synchronously. Because the number of combinations grows exponentially, even a small input can consume excessive CPU and memory resources, potentially crashing the Node.js process.


How can this vulnerability impact me? :

This vulnerability can lead to a denial of service condition by exhausting CPU and memory resources on the affected system. An attacker can cause the Node.js process using the vulnerable library to crash by supplying specially crafted input patterns, resulting in service downtime or disruption.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

I don't know


What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability, upgrade the @isaacs/brace-expansion package to version 5.0.1 or later, where the issue has been patched.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart