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

CVE-2021-23624 — dotty

CRITICALFix: deoxxa/dotty@88f6186

CVE-2021-23624 is a critical-severity (CVSS 9.8) CWE-843 vulnerability in dotty. 1 public exploit reference exists, so weaponization risk is real. A fix is available for dotty — see the affected versions and patch details below.

Prototype Pollution in dotty

Also known asGHSA-6g47-63mv-qpghSNYK-JS-DOTTY-1577292
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Oct 4, 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
0.00%0.59%1.19%1.78%0.4%1.3%Apr 26Aug 26Oct 26

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

How urgent is this, really

CVE-2021-23624 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.

215other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
dottynpm
65Kdownloads / week

Description

This affects the package dotty before 0.1.2. A type confusion vulnerability can lead to a bypass of CVE-2021-25912 when the user-provided keys used in the path parameter are arrays.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmdottyall versions0.1.2npm install dotty@0.1.2

Affected Products

1 product · 1 configurations
Application
dottydotty_project
< 0.1.2
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.

This affects the package dotty before 0.1.2. A type confusion vulnerabil…

snyk.ioNVDNov 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 dotty, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update dotty to 0.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-23624 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

This affects the package dotty before 0.1.2. A type confusion vulnerability can lead to a bypass of CVE-2021-25912 when the user-provided keys used in the path parameter are arrays.
O3 Security · Impact-Aware SCA

Is CVE-2021-23624 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2021-23624: dotty — Fixed in 0.1.2