Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

CVE-2021-3804 — @tarojs/helper

HIGHFix: nervjs/taro@acadb6c

CVE-2021-3804 is a high-severity (CVSS 7.5) CWE-1333 vulnerability in @tarojs/helper. 1 public exploit reference exists, so weaponization risk is real. A fix is available for @tarojs/helper — see the affected versions and patch details below.

Inefficient Regular Expression Complexity in taro

Also known asGHSA-468q-v4jj-485h
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Sep 30, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2021-3804 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

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.

145other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
@tarojs/helpernpm
31Kdownloads / week

Description

taro is vulnerable to Inefficient Regular Expression Complexity

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npm@tarojs/helperall versions3.3.9npm install @tarojs/helper@3.3.9

Affected Products

1 product · 1 configurations
Application
tarotaro
< 3.3.9
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

taro is vulnerable to Inefficient Regular Expression Complexity

huntr.devNVDSep 2021

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @tarojs/helper, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update @tarojs/helper to 3.3.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-3804 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

taro is vulnerable to Inefficient Regular Expression Complexity
O3 Security · Impact-Aware SCA

Is CVE-2021-3804 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2021-3804: @tarojs/helper — Fixed in 3.3.9