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

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. O3 Security confirms whether CVE-2021-3804 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Inefficient Regular Expression Complexity in taro

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

Real-World Exposure

1 pkg affected
📦@tarojs/helper

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

taro is vulnerable to Inefficient Regular Expression Complexity

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npm@tarojs/helperall versions3.3.9
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.

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  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.

  4. How O3 protects you

    O3 pinpoints whether CVE-2021-3804 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2021-3804. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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

Is CVE-2021-3804 in your dependencies?

O3 detects CVE-2021-3804 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

CVE-2021-3804: Inefficient Regular… | O3 Security