Skip to content

← Public intelligence

npm package

@babel/core

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Low, CVSS 3.2npmPublished

    @babel/core: Arbitrary File Read via sourceMappingURL Comment

    CVE-2026-49356 · GHSA-4x5r-pxfx-6jf8

    Affected
    • npm @babel/core >= 8.0.0-alpha.0, < 8.0.0-rc.6; < 7.29.6
    Fixed in
    8.0.0-rc.67.29.6· Vendor fix available
    Issue
    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…

    Recommended action: Upgrade to 8.0.0-rc.6 (pre-release) or 7.29.6 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.devSource checked Evidence →