taro-css-to-react-native Regular Expression Denial of Service vulnerabilityGHSA-f5xg-cfpj-2mw6
MEDIUMFix: NervJS/taro#17619GHSA-f5xg-cfpj-2mw6 is a medium-severity (CVSS 4.3) Uncontrolled Resource Consumption vulnerability in taro-css-to-react-native. A fix is available for taro-css-to-react-native — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-f5xg-cfpj-2mw6.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
taro-css-to-react-nativenpmDescription
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | taro-css-to-react-native | all versions | 4.1.2npm install taro-css-to-react-native@4.1.2 |
Affected Products
tarotaroDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for taro-css-to-react-native, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update taro-css-to-react-native to 4.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f5xg-cfpj-2mw6 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is GHSA-f5xg-cfpj-2mw6 in your dependencies?
Find it across npm, including transitive dependencies.