VulnerabilityPublished 9 Jun 2025

CVE-2025-5896: tarojs taro · ReDoS

Affects tarojs taroSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 11:42 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 26 Oct 2026.

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 or the CVSS exploit maturity 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
tarojs taro	Affected =4.1.0 =4.1.1	Fixed in–

AI-suggested

European organizations should prioritize upgrading the tarojs taro framework to version 4.1.2 or later, which contains the patch addressing this vulnerability. In addition to upgrading, organizations should implement input validation and sanitization to limit the complexity and length of inputs processed by the vulnerable regular expressions. Monitoring application performance metrics and setting thresholds for unusual CPU usage can help detect potential exploitation attempts early. Employing Web Application Firewalls (WAFs) with rules to detect and block suspicious payloads targeting regex processing can further reduce risk. For development teams, reviewing and refactoring regular expressions to avoid catastrophic backtracking and using regex libraries or engines that provide safeguards against ReDoS attacks is recommended. Finally, maintaining an inventory of applications and dependencies using tarojs taro will ensure timely patch management and vulnerability response.

Description

A vulnerability was found in tarojs taro up to 4.1.1. It has been declared as problematic. This vulnerability affects unknown code of the file taro/packages/css-to-react-native/src/index.js. The manipulation leads to inefficient regular expression complexity. The attack can be initiated remotely. Upgrading to version 4.1.2 is able to address this issue. The name of the patch is c2e321a8b6fc873427c466c69f41ed0b5e8814bf. It is recommended to upgrade the affected component.

Impact

For European organizations using the tarojs taro framework, particularly versions 4.1.0 and 4.1.1, this vulnerability could lead to service disruptions due to resource exhaustion caused by maliciously crafted inputs exploiting the inefficient regular expression. This can affect web applications or services relying on taro for CSS to React Native transformations, potentially causing denial of service conditions. While the vulnerability does not allow data breaches or code execution, the availability impact can disrupt business operations, degrade user experience, and increase operational costs due to mitigation efforts. Organizations in sectors with high availability requirements, such as finance, healthcare, and e-commerce, may face operational risks. Additionally, if exploited at scale, it could be used as part of a larger distributed denial of service (DDoS) campaign targeting applications using this framework.

Summary

CVE-2025-5896 is a medium severity vulnerability affecting the tarojs taro framework versions up to 4.1.1, specifically in the file taro/packages/css-to-react-native/src/index.js. The issue arises from inefficient regular expression complexity, which can be exploited remotely without requiring user interaction or elevated privileges. This vulnerability is a form of Regular Expression Denial of Service (ReDoS), where an attacker crafts input that causes the regular expression engine to consume excessive CPU resources, leading to degraded performance or service unavailability. The vulnerability does not compromise confidentiality or integrity directly but impacts availability by potentially causing application slowdowns or crashes. The vendor has addressed this issue in version 4.1.2, with a patch identified by commit c2e321a8b6fc873427c466c69f41ed0b5e8814bf. No known exploits are currently reported in the wild. The CVSS 4.0 vector indicates network attack vector, low attack complexity, no privileges required, no user interaction, and low impact on availability, with no impact on confidentiality or integrity, resulting in a score of 5.3 (medium severity).

References

Community reviews

Loading reviews…