CVE-2026-102277
Description
A flaw was found in brace-expansion. A remote attacker can cause a Denial of Service (DoS) by supplying specially crafted string patterns with repeated closing braces. Processing these malformed patterns causes the string expansion logic to repeatedly rescan the entire input, leading to excessive processor and memory consumption that can temporarily block the application event loop.
Statement
A moderate-impact denial of service vulnerability was found in brace-expansion, an npm package bundled as a dependency in a large number of Red Hat products that ship Node.js-based components. When an application passes attacker-controlled input to the expand function, a remote unauthenticated attacker can supply a crafted {a},b}-shaped pattern containing many trailing closing braces. The parser rewrites the string and restarts its scan once for each trailing closing brace, and every pass rescans the entire input, resulting in quadratic CPU time and memory consumption. This can block the Node.js event loop of the affected process and temporarily disrupt application availability; the process recovers once the expansion completes, making this a recoverable CPU denial of service with no impact on confidentiality or integrity. The large majority of Red Hat product streams that ship a bundled copy of brace-expansion are affected; a small number of shipped components are marked not affected because the vulnerable code is not present in the shipped version or because those components do not include brace-expansion. For most affected streams the fix is deferred to a routine future component update, since the flaw is a recoverable, availability-only denial of service of low severity; the residual risk of deferral is temporary CPU and memory pressure and event-loop blocking when an attacker is able to supply crafted brace patterns to an affected application's expansion call. For streams where remediation is delegated, the maintainers of the bundled component are pursuing a fix, and a small number of streams have already shipped an update that remediates the issue. The Red Hat severity of MODERATE (CVSS 3.1 score 5.3, vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L) is consistent with the upstream assessment, so there is no meaningful difference from upstream severity.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. Updating the bundled brace-expansion dependency to a version that contains the upstream fix (1.1.21, 2.1.7, 3.0.9, or 5.0.12, depending on the major version in use) resolves the issue.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.3 | N/A | 5.3 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | None |
| Integrity Impact | None | N/A | None |
| Availability Impact | Low | N/A | Low |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.