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

CVE-2021-23568

CRITICALFix: eggjs/extend2@aa332a5

CVE-2021-23568 is a critical-severity (CVSS 9.8) CWE-1321 vulnerability in extend2. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2021-23568 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Prototype Pollution in extend2

Also known asGHSA-gjm5-83cw-p3p2
Published
Jan 10, 2022
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
📦extend2

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

The package extend2 before 1.0.1 are vulnerable to Prototype Pollution via the extend function due to unsafe recursive merge.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmextend2all versions1.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 extend2. 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 extend2 to 1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-23568 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-23568 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-23568. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The package extend2 before 1.0.1 are vulnerable to Prototype Pollution via the extend function due to unsafe recursive merge.
O3 Security · Impact-Aware SCA

Is CVE-2021-23568 in your dependencies?

O3 detects CVE-2021-23568 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-23568: Prototype Pollution in… | O3 Security