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.
Original description
The description as published by the source.
Impact
Using @babel/core to compile maliciously crafted code can allow ab attacker to read any source map from the system that is running Babel, if these conditions are all true:
- the attacker controls the input source code
- the attacker can read the output source code
- the attacker knows the path of the source map file that they want to read
Users that only compile trusted code are not impacted.
Patches
The vulnerability has been fixed in @babel/core@7.29.6 and @babel/core@8.0.0-rc.6.
Workarounds
Callers can mitigate the issue without upgrading by setting inputSourceMap: false in their Babel options.
Callers can also manually extract the #sourceMappingURL comment from the input source code, validate whether the source map that it links to is allowed to be read, and if it is pass an object to inputSourceMap (passing false when it's not).
Credits
Thanks Teodor-Cristian Radoi for reporting the vulnerability.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
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.
Path traversal (CWE-22) exists in @babel/core. Attackers reach the vulnerable code path via inputSourceMap without authentication.
Check the vendor advisory for the affected versions of @babel/core. Attack surface: inputSourceMap / false.
Severity: Low (CVSS 3.2/10). Risk of unauthorized operations or information disclosure.
Update to 7.29.6.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @babel/core to 7.29.6ステージング環境で 7.29.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-49356 node-babel7
- Ubuntu UBUNTU-CVE-2026-49356 babel
References
- package github.com
- web github.com
- web babeljs.io
- web github.com
- web nvd.nist.gov