Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

CVE-2021-3807

HIGH

Inefficient Regular Expression Complexity in chalk/ansi-regex

Also known asGHSA-93q8-gq69-wqmw
Published
Sep 17, 2021
Updated
Jul 8, 2026
Affected
4 pkgs
Patched
4 / 4
Exploits
1 known

EPSS Exploitation Probability

via FIRST.org ↗
3.6%probability of exploitation in next 30 days
Lower Risk88th percentile+0.25%
0.00%1.53%3.05%4.58%0.1%3.6%Jan 26May 26Jul 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

4 pkgs affected
📦ansi-regex📦ansi-regex📦ansi-regex📦ansi-regex

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

ansi-regex is vulnerable to Inefficient Regular Expression Complexity

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
📦npmansi-regex6.0.0&&< 6.0.16.0.1
📦npmansi-regex5.0.0&&< 5.0.15.0.1
📦npmansi-regex4.0.0&&< 4.1.14.1.1
📦npmansi-regex3.0.0&&< 3.0.13.0.1
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 ansi-regex. 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 ansi-regex to 6.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-3807 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-3807 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-3807. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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

Is CVE-2021-3807 in your dependencies?

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