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

CVE-2021-23403 — ts-nodash

HIGHFix: BadOPCode/NoDash@b9cc2b3

CVE-2021-23403 is a high-severity (CVSS 7.3) CWE-1321 vulnerability in ts-nodash. 2 public exploit references exist, so weaponization risk is real. A fix is available for ts-nodash — see the affected versions and patch details below.

Prototype Pollution in ts-nodash

Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Oct 5, 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.79%1.12%1.45%1.79%1.3%1.3%1.3%Jul 26Oct 26Oct 26

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

How urgent is this, really

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

Where this sits among everything scored

Of 385,738 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.

1other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
ts-nodashnpm
135downloads / week

Description

All versions of package ts-nodash are vulnerable to Prototype Pollution via the Merge() function due to lack of validation input.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmts-nodashall versions1.2.7npm install ts-nodash@1.2.7

Affected Products

1 product · 1 configurations
Application
ts-nodashts-nodash_project
all
Exploits & PoCs
2

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

All versions of package ts-nodash are vulnerable to Prototype Pollution …

snyk.ioNVDJul 2021

All versions of package ts-nodash are vulnerable to Prototype Pollution …

github.comNVDJul 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 ts-nodash, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

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

`ts-nodash` before version 1.2.7 is vulnerable to Prototype Pollution via the Merge() function due to lack of validation input.
O3 Security · Impact-Aware SCA

Is CVE-2021-23403 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2021-23403: ts-nodash — Fixed in 1.2.7