CVE-2025-5897VulnerabilityPublished 9 Jun 2025

CVE-2025-5897: vuejs vue-cli · ReDoS

Affects vuejs vue-cliSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
vuejs vue-cli	Affected =5.0.0 =5.0.1 =5.0.2 =5.0.3 =5.0.4 =5.0.5 =5.0.6 =5.0.7 =5.0.8	Fixed in–

AI-suggested

To mitigate CVE-2025-5897, European organizations should: 1) Immediately audit their development and build environments to identify usage of vue-cli versions 5.0.0 through 5.0.8, particularly where the PWA plugin and Markdown processing are enabled. 3) Implement input validation and sanitization for any Markdown content processed during builds to reduce the risk of malicious payloads triggering the regex complexity issue. 4) Monitor build server resource utilization and set thresholds to detect abnormal CPU spikes that may indicate exploitation attempts. 5) Restrict network access to build servers to trusted sources only, minimizing exposure to remote attacks. 6) Incorporate vulnerability scanning and dependency checks into CI/CD pipelines to detect vulnerable vue-cli versions proactively. 7) Educate development teams about the risks of processing untrusted content in build tools and encourage best practices for secure build configurations.

Description

A vulnerability was found in vuejs vue-cli up to 5.0.8. It has been rated as problematic. This issue affects the function HtmlPwaPlugin of the file packages/@vue/cli-plugin-pwa/lib/HtmlPwaPlugin.js of the component Markdown Code Handler. The manipulation leads to inefficient regular expression complexity. The attack may be initiated remotely.

Impact

For European organizations, the impact of CVE-2025-5897 primarily concerns the stability and availability of development and continuous integration/continuous deployment (CI/CD) environments that utilize vue-cli versions up to 5.0.8. Organizations relying on vue-cli for building Vue.js applications, especially those integrating PWA features with Markdown content, may experience service disruptions or delays due to resource exhaustion caused by maliciously crafted inputs. This can lead to slowed development cycles, delayed deployments, and potential downtime of build servers. While the vulnerability does not directly compromise data confidentiality or integrity, the denial-of-service aspect can indirectly affect business operations, particularly for companies with tight release schedules or those offering real-time application updates. Given the widespread adoption of Vue.js and vue-cli in European tech sectors, including startups and enterprises in software development, e-commerce, and digital services, the vulnerability poses a moderate operational risk. Additionally, organizations in regulated industries with strict uptime and availability requirements may face compliance challenges if this vulnerability is exploited.

References

Community reviews

Loading reviews…