CVE-2025-27789
ADVISORY - githubSummary
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 use duplicated named capturing groups, and target any browser older than Chrome/Edge 126, Opera 112, Firefox 129, Safari 17.4, or Node.js 23
- you use any named capturing groups, and target any browser older than Chrome 64, Opera 71, Edge 79, Firefox 78, Safari 11.1, or Node.js 10
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.
Common Weakness Enumeration (CWE)
Inefficient Regular Expression Complexity
Inefficient Regular Expression Complexity
GitHub
2.5
CVSS SCORE
6.2mediumPackage | Type | OS Name | OS Version | Affected Ranges | Fix Versions |
---|---|---|---|---|---|
@babel/helpers | npm | - | - | <7.26.10 | 7.26.10 |
@babel/helpers | npm | - | - | >=8.0.0-alpha.0,<8.0.0-alpha.16 | 8.0.0-alpha.17 |
@babel/runtime | npm | - | - | <7.26.10 | 7.26.10 |
@babel/runtime | npm | - | - | >=8.0.0-alpha.0,<8.0.0-alpha.16 | 8.0.0-alpha.17 |
@babel/runtime-corejs2 | npm | - | - | <7.26.10 | 7.26.10 |
@babel/runtime-corejs2 | npm | - | - | >=8.0.0-alpha.0,<8.0.0-alpha.16 | 8.0.0-alpha.17 |
@babel/runtime-corejs3 | npm | - | - | <7.26.10 | 7.26.10 |
@babel/runtime-corejs3 | npm | - | - | >=8.0.0-alpha.0,<8.0.0-alpha.16 | 8.0.0-alpha.17 |
CVSS:3 Severity and metrics
The CVSS metrics represent different qualitative aspects of a vulnerability that impact the overall score, as defined by the CVSS Specification.
The vulnerable component is not bound to the network stack and the attacker's path is via read/write/execute capabilities. Either: The attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.
The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
The vulnerable system can be exploited without interaction from any user.
An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
There is no loss of confidentiality.
There is no loss of trust or accuracy within the impacted component.
There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component.
NIST
2.5
CVSS SCORE
6.2mediumUbuntu
-
CVSS SCORE
N/AmediumChainguard
CGA-3phx-qxx7-8vqw
-
Chainguard
CGA-46ch-ch69-qmcw
-
Chainguard
CGA-g6rv-q8mg-pp3f
-
Chainguard
CGA-g7xj-r4gh-6jhr
-
Chainguard
CGA-j8cm-jvwv-37vw
-
Chainguard
CGA-m6wq-wmrx-cp34
-
Chainguard
CGA-mwpg-44pj-qpj8
-
Chainguard
CGA-qgr4-9ff9-9j58
-
Chainguard
CGA-rh34-93h2-vxqh
-
Chainguard
CGA-v5pv-jcc5-rq8m
-