Advisory

GHSA-968p-4wvh-cqc8

Also known as: CVE-2025-27789

Summary

Babel has inefficient RegExp complexity in generated code with .replace when transpiling named capturing groups

Details

Impact

When using Babel to compile regular expression named capturing groups, Babel will generate a polyfill for the .replace method that has quadratic complexity on some specific replacement pattern strings (i.e. the second argument passed to .replace).

Your generated code is vulnerable if _all_ the following conditions are true:

  • You use Babel to compile regular expression named capturing groups
  • You use the .replace method on a regular expression that contains named capturing groups
  • Your code uses untrusted strings as the second argument of `.replace`

If you are using @babel/preset-env with the `targets` option, the transform that injects the vulnerable code is automatically enabled if:

You can verify what transforms @babel/preset-env is using by enabling the `debug` option.

Patches

This problem has been fixed in @babel/helpers and @babel/runtime 7.26.10 and 8.0.0-alpha.17, please upgrade. It's likely that you do not directly depend on @babel/helpers, and instead you depend on @babel/core (which itself depends on @babel/helpers). Upgrading to @babel/core 7.26.10 is not required, but it guarantees that you are on a new enough @babel/helpers version.

Please note that just updating your Babel dependencies is not enough: you will also need to re-compile your code.

Workarounds

If you are passing user-provided strings as the second argument of .replace on regular expressions that contain named capturing groups, validate the input and make sure it does not contain the substring $< if it's then not followed by > (possibly with other characters in between).

References

This vulnerability was reported and fixed in https://github.com/babel/babel/pull/17173.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2025-03-11 20:30 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

@babel/helpers

npm · All systems

Affected

  • introduced 0, fixed 7.26.10 (semver)

Fixed versions

7.26.10

Fix

@babel/runtime

npm · All systems

Affected

  • introduced 0, fixed 7.26.10 (semver)

Fixed versions

7.26.10

Fix

@babel/runtime-corejs2

npm · All systems

Affected

  • introduced 0, fixed 7.26.10 (semver)

Fixed versions

7.26.10

Fix

@babel/runtime-corejs3

npm · All systems

Affected

  • introduced 0, fixed 7.26.10 (semver)

Fixed versions

7.26.10

Fix

@babel/helpers

npm · All systems

Affected

  • introduced 8.0.0-alpha.0, fixed 8.0.0-alpha.17 (semver)

Fixed versions

8.0.0-alpha.17

Fix

@babel/runtime

npm · All systems

Affected

  • introduced 8.0.0-alpha.0, fixed 8.0.0-alpha.17 (semver)

Fixed versions

8.0.0-alpha.17

Fix

@babel/runtime-corejs2

npm · All systems

Affected

  • introduced 8.0.0-alpha.0, fixed 8.0.0-alpha.17 (semver)

Fixed versions

8.0.0-alpha.17

Fix

@babel/runtime-corejs3

npm · All systems

Affected

  • introduced 8.0.0-alpha.0, fixed 8.0.0-alpha.17 (semver)

Fixed versions

8.0.0-alpha.17

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences