Answer in brief
CVE-2026-49356 records a Low severity (CVSS 3.2) path traversal vulnerability in @babel/core: Arbitrary File Read via sourceMappingURL Comment. The source record does not mark it as known exploited. 2 affected packages are mapped in the feed.
Answer in brief
CVE-2026-49356 records a Low severity (CVSS 3.2) path traversal vulnerability in @babel/core: Arbitrary File Read via sourceMappingURL Comment. The source record does not mark it as known exploited. 2 affected packages are mapped in the feed.
Update @babel/core to 8.0.0-rc.6; @babel/core to 7.29.6 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanPath Traversal describes the vulnerability class recorded for this advisory. The current record does not mark CVE-2026-49356 as known exploited; continue to monitor the source for status changes. The feed includes package mappings that can be checked against lockfiles and deployed manifests.
| Package | Affected range | Fixed version |
|---|---|---|
| @babel/corenpm | >=8.0.0-alpha.0,<8.0.0-rc.5 | 8.0.0-rc.6 |
| @babel/corenpm | <=7.29.0 | 7.29.6 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
CVE-2026-49356 records a Low severity (CVSS 3.2) path traversal vulnerability in @babel/core: Arbitrary File Read via sourceMappingURL Comment. The source record does not mark it as known exploited. 2 affected packages are mapped in the feed.
The source record does not mark it as known exploited.
Check lockfiles and deployed manifests for @babel/core, @babel/core.
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardUpdate @babel/core to 8.0.0-rc.6; @babel/core to 7.29.6 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanPath Traversal describes the vulnerability class recorded for this advisory. The current record does not mark CVE-2026-49356 as known exploited; continue to monitor the source for status changes. The feed includes package mappings that can be checked against lockfiles and deployed manifests.
| Package | Affected range | Fixed version |
|---|---|---|
| @babel/corenpm | >=8.0.0-alpha.0,<8.0.0-rc.5 | 8.0.0-rc.6 |
| @babel/corenpm | <=7.29.0 | 7.29.6 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
CVE-2026-49356 records a Low severity (CVSS 3.2) path traversal vulnerability in @babel/core: Arbitrary File Read via sourceMappingURL Comment. The source record does not mark it as known exploited. 2 affected packages are mapped in the feed.
The source record does not mark it as known exploited.
Check lockfiles and deployed manifests for @babel/core, @babel/core.
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard## 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/[email protected]` and `@babel/[email protected]`. ## Workarounds Callers can mitigate the issue without upgrading by setting [`inputSourceMap: false`](https://babeljs.io/docs/options#inputsourcemap) 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.
## 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/[email protected]` and `@babel/[email protected]`. ## Workarounds Callers can mitigate the issue without upgrading by setting [`inputSourceMap: false`](https://babeljs.io/docs/options#inputsourcemap) 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.