Regularly check for vulnerabilities

Oct 13, 2025 by thesweetdesigns.com 11 views

Compiler-CLI 15.2.10.tgz: 1 Vulnerability (Highest Severity is: 6.2)

In the world of software development, security is a top priority. One of the most critical aspects of ensuring the security of our applications is to identify and address vulnerabilities in our dependencies. In this article, we will discuss a vulnerability found in the compiler-cli-15.2.10.tgz package, which has a severity of 6.2.

CVE	Severity	CVSS	Dependency	Type	Fixed in (compiler-cli version)	Remediation Possible**	Reachability
CVE-2025-27789	Medium	6.2	helpers-7.24.8.tgz	Transitive	N/A*	❌

For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.

CVE-2025-27789

Vulnerable Library - helpers-7.24.8.tgz

Library home page: https://registry.npmjs.org/@babel/helpers/-/helpers-7.24.8.tgz

Path to dependency file: /frontend/package.json

Path to vulnerable library: /frontend/node_modules/@babel/helpers/package.json

Dependency Hierarchy:

compiler-cli-15.2.10.tgz (Root Library)
- core-7.19.3.tgz
  - :x: helpers-7.24.8.tgz (Vulnerable Library)

Found in HEAD commit: 46f9017bf07d9afe8f4c8706e6bb2bdfc9524486

Found in base branch: main

Vulnerability Details

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.

Publish Date: 2025-03-11

URL: CVE-2025-27789

CVSS 3 Score Details (6.2)

Base Score Metrics:

Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://github.com/advisories/GHSA-968p-4wvh-cqc8

Release Date: 2025-03-11

Fix Resolution: 7.26.10

In conclusion, the compiler-cli-15.2.10.tgz package has a vulnerability with a severity of 6.2. This vulnerability is caused by a transitive dependency on helpers-7.24.8.tgz, which has a quadratic complexity on some specific replacement pattern strings. To fix this vulnerability, we need to upgrade the version of @babel/helpers to 7.26.10 or later. This will ensure that the generated code is not vulnerable to this issue. It's essential to regularly check for vulnerabilities in our dependencies and address them promptly to ensure the security of our applications.

Upgrade @babel/helpers: Upgrade the version of @babel/helpers to 7.26.10 or later to fix the vulnerability.
Regularly check for vulnerabilities: Regularly check for vulnerabilities in our dependencies and address them promptly to ensure the security of our applications.
Use a vulnerability scanner: Use a vulnerability scanner to identify vulnerabilities in our dependencies and ensure that we are aware of any potential security issues.

By following these recommendations, we can ensure the security of our applications and prevent potential security issues.
Q&A: Compiler-CLI 15.2.10.tgz Vulnerability

In our previous article, we discussed a vulnerability found in the compiler-cli-15.2.10.tgz package, which has a severity of 6.2. In this article, we will answer some frequently asked questions (FAQs) related to this vulnerability.

A: The compiler-cli-15.2.10.tgz package is a JavaScript compiler that is used to compile regular expression named capturing groups. It is a part of the Babel compiler.

A: The vulnerability in the compiler-cli-15.2.10.tgz package is caused by a transitive dependency on helpers-7.24.8.tgz, which has a quadratic complexity on some specific replacement pattern strings. This can lead to a denial-of-service (DoS) attack.

A: To identify if your application is affected by this vulnerability, you can check the version of @babel/helpers in your package.json file. If it is less than 7.26.10, your application may be affected.

A: To fix this vulnerability, you need to upgrade the version of @babel/helpers to 7.26.10 or later. This will ensure that the generated code is not vulnerable to this issue.

A: No, there is no known workaround to fix this vulnerability. You need to upgrade the version of @babel/helpers to 7.26.10 or later to fix the issue.

A: To prevent similar vulnerabilities in the future, you can:

Regularly check for vulnerabilities in your dependencies.
Use a vulnerability scanner to identify potential security issues.
Keep your dependencies up-to-date with the latest versions.

A: The impact of this vulnerability is a denial-of-service (DoS) attack, which can cause your application to become unresponsive or crash.

A: Yes, this vulnerability is critical and should be addressed promptly to ensure the security of your application.

In conclusion, the compiler-cli-15.2.10.tgz package has a vulnerability with a severity of 6.2. This vulnerability is caused by a transitive dependency on helpers-7.24.8.tgz, which has a quadratic complexity on some specific replacement pattern strings. To fix this vulnerability, you need to upgrade the version of @babel/helpers to 7.26.10 or later. We hope this Q&A article has helped you understand the vulnerability and how to fix it.