Skip to content

chore(deps): update dependency @babel/core to v7.29.6 [security] - #1067

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-babel-core-vulnerability
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-babel-core-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Jun 30, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@babel/core (source) 7.29.0 → 7.29.6 age confidence

@​babel/core: Arbitrary File Read via sourceMappingURL Comment

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

More information

Details

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.

Severity

  • CVSS Score: 3.2 / 10 (Low)
  • Vector String: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

babel/babel (@​babel/core)

v7.29.6

Compare Source

v7.29.6 (2026-05-25)

🐛 Bug Fix
Committers: 3

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added dependencies Pull requests that update a dependency file internal labels Jun 30, 2026
@renovate
renovate Bot force-pushed the renovate/npm-babel-core-vulnerability branch 2 times, most recently from df4dc72 to 0422ad9 Compare July 16, 2026 15:37
@renovate
renovate Bot force-pushed the renovate/npm-babel-core-vulnerability branch 2 times, most recently from 8e02a6a to 2a9a731 Compare July 24, 2026 19:39
@renovate
renovate Bot force-pushed the renovate/npm-babel-core-vulnerability branch from 2a9a731 to a271bf4 Compare July 30, 2026 16:33
@renovate
renovate Bot force-pushed the renovate/npm-babel-core-vulnerability branch 2 times, most recently from c311346 to 205ac49 Compare August 14, 2026 20:36
@renovate
renovate Bot force-pushed the renovate/npm-babel-core-vulnerability branch from 205ac49 to 3d1d6ed Compare August 26, 2026 18:56
@renovate
renovate Bot force-pushed the renovate/npm-babel-core-vulnerability branch 4 times, most recently from aa8ca5b to 8a8abb7 Compare September 9, 2026 20:02
@renovate
renovate Bot force-pushed the renovate/npm-babel-core-vulnerability branch 2 times, most recently from 7eb63ce to 141c44d Compare September 15, 2026 15:02
@renovate
renovate Bot force-pushed the renovate/npm-babel-core-vulnerability branch from 141c44d to 4f5a79f Compare September 18, 2026 19:35
@renovate
renovate Bot force-pushed the renovate/npm-babel-core-vulnerability branch from 4f5a79f to db2ba45 Compare September 25, 2026 02:45

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file internal

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants