CVE-2026-49356: @babel/core · Arbitrary File Read via sourceMappingURL Comment
Affects @babel/coreSource GCVE Database
Not known to be exploited · CVSS 3.2 Low : upgrade to 8.0.0-rc.6 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 8.0.0-rc.6, 7.29.6
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade @babel/core to 8.0.0-rc.6; @babel/core to 7.29.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npm@babel/core | Affected
| Fixed in
|
| npm@babel/core | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade @babel/core to version 7.29.6 or later. Alternatively, callers can mitigate without upgrading by setting the Babel option inputSourceMap to false, or by manually validating and controlling the sourceMappingURL comment in input source code before passing it to Babel.
Description
A vulnerability in @babel/core prior to version 7.29.6 allows an attacker who controls input source code and can read the output source code to read arbitrary source map files on the system running Babel. This requires the attacker to know the path of the source map file they want to access. Users compiling only trusted code are not affected. The issue is fixed in @babel/core version 7.29.6 and later.