← Back
CVE-2026-49356
low
CVSS 3.2
Path Traversal in @babel/core (CVE-2026-49356)
Summary
path traversal in @babel/core (CVE-2026-49356). Risk of unauthorized operations or information disclosure. Exploitable via ``inputSourceMap``. Mitigation: upgrade to `7.29.6` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-49356** has been found in @babel/core.
Attackers can target a specific entry point like ``inputSourceMap`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.2/10.
What to do: upgrade @babel/core to **7.29.6** or later.
If unsure, ask your IT team or search "@babel/core CVE-2026-49356" on the vendor's site.
CVE-2026-49356 (@babel/core) — CWE-22 / CVSS v3 3.2
Attack vector: local / unauthenticated / no user interaction
Attack surface: `inputSourceMap` / `false`
Patched: `7.29.6` — 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
**Path traversal** (CWE-22) exists in @babel/core. Attackers reach the vulnerable code path via ``inputSourceMap`` without authentication.
📍 Affected scope
@babel/core — . Attack surface: `inputSourceMap` / `false`.
🔥 Severity
Severity: Low (CVSS 3.2/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **7.29.6**.
🛡️ 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 '@babel/core' .` 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 '@babel/core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@babel/core` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @babel/core to 7.29.6ステージング環境で 7.29.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@babel/core
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"7.29.6"}]}]