← Back
CVE-2026-13149
Vulnerability in brace-expansion (CVE-2026-13149)
Summary
vulnerability in brace-expansion (CVE-2026-13149). Risk of unauthorized operations or information disclosure. Exploitable via ``expand_``. Mitigation: upgrade to `2.1.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-13149** has been found in brace-expansion.
Attackers can target a specific entry point like ``expand_`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade brace-expansion to **2.1.2** or later.
If unsure, ask your IT team or search "brace-expansion CVE-2026-13149" on the vendor's site.
CVE-2026-13149 (brace-expansion) — CWE-400 /
Attack surface: `expand_` / `post`
Patched: `2.1.2` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-400) exists in brace-expansion. Attackers reach the vulnerable code path via ``expand_`` without authentication.
📍 Affected scope
brace-expansion — . Attack surface: `expand_` / `post`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.1.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'brace-expansion' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'brace-expansion' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `brace-expansion` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade brace-expansion to 2.1.2ステージング環境で 2.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
brace-expansion
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.1.2"}]}]
References
- web https://github.com/juliangruber/brace-expansion/commit/c7e33ec13ac1a684c116720843ce24e208611754
- web https://www.npmjs.com/package/brace-expansion
- web https://github.com/juliangruber/brace-expansion/security/advisories/GHSA-3jxr-9vmj-r5cp
- web https://nvd.nist.gov/vuln/detail/CVE-2026-13149
- web https://github.com/juliangruber/brace-expansion/pull/122
- web https://github.com/juliangruber/brace-expansion/pull/123
- web https://github.com/juliangruber/brace-expansion/commit/835d6be91201122d9adffb0c0c8c094189ace265
- web https://github.com/juliangruber/brace-expansion/commit/d74e63030c012e3b7ae81657b8d665619cd51b95
- web https://github.com/juliangruber/brace-expansion/releases/tag/v1.1.16
- web https://github.com/juliangruber/brace-expansion/releases/tag/v2.1.2
- web https://github.com/juliangruber/brace-expansion/releases/tag/v5.0.7
- web https://github.com/advisories/GHSA-3jxr-9vmj-r5cp