CVE-2025-27789: Inefficient RexExp complexity in generated code with .replace when transpiling named capturing groups
Noroxi assessment
Priority: Monitor (action score 24/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.56% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: @babel/helpers (npm) 8.0.0-alpha.17, 7.26.10; @babel/runtime (npm) 8.0.0-alpha.17, 7.26.10; @babel/runtime-corejs2 (npm) 8.0.0-alpha.17, 7.26.10.
Low priority for now. Upgrade to @babel/helpers (npm) 8.0.0-alpha.17, 7.26.10; @babel/runtime (npm) 8.0.0-alpha.17, 7.26.10; @babel/runtime-corejs2 (npm) 8.0.0-alpha.17, 7.26.10 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Babel is a compiler for writing next generation JavaScript. When using versions of Babel prior to 7.26.10 and 8.0.0-alpha.17 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`). Generated code is vulnerable if all the following conditions are true: Using Babel to compile regular expression named capturing groups, using the `.replace` method on a regular expression that contains named capturing groups, and the code using untrusted strings as the second argument of `.replace`. This problem has been fixed in `@babel/helpers` and `@babel/runtime` 7.26.10 and 8.0.0-alpha.17. It's likely that individual users do not directly depend on `@babel/helpers`, and instead depend on `@babel/core` (which itself depends on `@babel/helpers`). Upgrading to `@babel/core` 7.26.10 is not required, but it guarantees use of a new enough `@babel/helpers` version. Note that just updating Babel dependencies is not enough; one will also need to re-compile the code. No known workarounds are available.
- Published
- Mar 11, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.5% · 47th percentile
- CWE
- CWE-1333
Report tools
Action score
24
Low priority for now.
- CVSS
- 24 / 40 · 6.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 6.2
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
babel babel
- < 7.26.10, >= 8.0.0-alpha.0, < 8.0.0-alpha.17affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| npm | @babel/helpers | from 8.0.0-alpha.0 · before 8.0.0-alpha.17 | 8.0.0-alpha.17 |
| npm | @babel/helpers | before 7.26.10 | 7.26.10 |
| npm | @babel/runtime | from 8.0.0-alpha.0 · before 8.0.0-alpha.17 | 8.0.0-alpha.17 |
| npm | @babel/runtime | before 7.26.10 | 7.26.10 |
| npm | @babel/runtime-corejs2 | from 8.0.0-alpha.0 · before 8.0.0-alpha.17 | 8.0.0-alpha.17 |
| npm | @babel/runtime-corejs2 | before 7.26.10 | 7.26.10 |
| npm | @babel/runtime-corejs3 | from 8.0.0-alpha.0 · before 8.0.0-alpha.17 | 8.0.0-alpha.17 |
| npm | @babel/runtime-corejs3 | before 7.26.10 | 7.26.10 |
Same product
babel: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-44728Improper Control of Generation of Code when compiling specifically crafted malicious code with @babel/plugin-transform-modules-systemjs31Monitor
- CVE-2026-49356Babel: Arbitrary File Read via sourceMappingURL Comment in @babel/core14Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| npm:@babel/helpers | 7.26.10 | Package registry (OSV) |
| npm:@babel/helpers | 8.0.0-alpha.17 | Package registry (OSV) |
| npm:@babel/runtime | 7.26.10 | Package registry (OSV) |
| npm:@babel/runtime | 8.0.0-alpha.17 | Package registry (OSV) |
| npm:@babel/runtime-corejs2 | 7.26.10 | Package registry (OSV) |
| npm:@babel/runtime-corejs2 | 8.0.0-alpha.17 | Package registry (OSV) |
| npm:@babel/runtime-corejs3 | 7.26.10 | Package registry (OSV) |
| npm:@babel/runtime-corejs3 | 8.0.0-alpha.17 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-1333 · Inefficient Regular Expression ComplexityCVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.