GHSA-qhr7-859c-m2p7

brace-expansion: DoS via uncontrolled recursion on nested brace groups causing stack exhaustion

High highest severity reported · also known as CVE-2026-102278

10
catalog tools match this advisory
0
ship the vulnerable code in their release binary (Go tools analyzed with govulncheck)
No
in the CISA KEV catalog
0.5%
EPSS for CVE-2026-102278, percentile 42

Catalog tools matching GHSA-qhr7-859c-m2p7

ToolVersion scannedPackageFixed inReleased binaryDeclared in or found inDispute
sysdig-inspect
Container Security › Runtime Security
0.12.1brace-expansion@1.1.11
npm
1.1.20not analyzedember-electron/backend/package-lock.jsonDispute
eslint-plugin-security
Static Application Security Testing (SAST) › Language-specific › JavaScript/Node.js
eslint-plugin-security-v4.2.1brace-expansion@1.1.11
npm
1.1.20not analyzedpackage-lock.jsonDispute
eslint-plugin-security
Static Application Security Testing (SAST) › Language-specific › JavaScript/Node.js
eslint-plugin-security-v4.2.1brace-expansion@1.1.18
npm
1.1.20not analyzedpackage-lock.jsonDispute
eslint-plugin-security
Static Application Security Testing (SAST) › Language-specific › JavaScript/Node.js
eslint-plugin-security-v4.2.1brace-expansion@2.0.1
npm
2.1.6not analyzedpackage-lock.jsonDispute
eslint-plugin-security
Static Application Security Testing (SAST) › Language-specific › JavaScript/Node.js
eslint-plugin-security-v4.2.1brace-expansion@2.1.4
npm
2.1.6not analyzedpackage-lock.jsonDispute
infisical
Secret Management
v0.167.4brace-expansion@1.1.14
npm
1.1.20not analyzedfrontend/package-lock.jsonDispute
infisical
Secret Management
v0.167.4brace-expansion@2.1.0
npm
2.1.6not analyzedfrontend/package-lock.jsonDispute
infisical
Secret Management
v0.167.4brace-expansion@5.0.9
npm
5.0.11not analyzedfrontend/package-lock.jsonDispute
KubeStellar Console
Kubernetes Security
v0.3.42brace-expansion@2.1.4
npm
2.1.6not analyzed.github/ga4-scripts/package-lock.jsonDispute
KubeStellar Console
Kubernetes Security
v0.3.42brace-expansion@5.0.9
npm
5.0.11not analyzedweb/package-lock.jsonDispute
gatekeeper
Policy as Code
v3.23.1brace-expansion@1.1.13
npm
1.1.20not analyzedwebsite/yarn.lockDispute
prowler
Cloud Security
5.47.0brace-expansion@1.1.18
npm
1.1.20not analyzedui/pnpm-lock.yamlDispute
prowler
Cloud Security
5.47.0brace-expansion@5.0.9
npm
5.0.11not analyzedui/pnpm-lock.yamlDispute
vet
Software Composition Analysis (SCA)
v1.20.0brace-expansion@5.0.9
npm
5.0.11not analyzedpnpm-lock.yamlDispute
cloudsplaining
Cloud Security
0.9.1brace-expansion@1.1.12
npm
1.1.20not analyzedpackage-lock.jsonDispute
cloudsplaining
Cloud Security
0.9.1brace-expansion@2.0.2
npm
2.1.6not analyzedpackage-lock.jsonDispute
slsa-verifier
Supply Chain Compliance
v2.7.1brace-expansion@1.1.11
npm
1.1.20not analyzedpackage-lock.jsonDispute
slsa-verifier
Supply Chain Compliance
v2.7.1brace-expansion@2.0.1
npm
2.1.6not analyzedpackage-lock.jsonDispute
snyk-cli
Software Composition Analysis (SCA)
v1.1308.3brace-expansion@1.1.11
npm
1.1.20not analyzedts-binary-wrapper/package-lock.jsonDispute

Vulnerabilities are known advisories that Grype matches against the dependencies declared in each project's release source (manifests and lockfiles, including development and build dependencies). A match does not mean the tool is exploitable: the vulnerable code may be unused, test-only, or not shipped in the released binary. KEV: listed in the CISA Known Exploited Vulnerabilities catalog. EPSS: FIRST's estimated probability of exploitation in the next 30 days. Both describe the vulnerability in general, not its exploitability through this tool; a match in a workflow file refers to a GitHub Action, not to shipped code. Released binary is only analyzed for Go tools with a Linux release binary; other tools show not analyzed.

Advisory sources

GitHub advisory GHSA-qhr7-859c-m2p7 · NVD CVE-2026-102278 · OSV GHSA-qhr7-859c-m2p7

Grype data sources: https://github.com/advisories/GHSA-qhr7-859c-m2p7