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

CVE-2021-23329 — nested-object-assign

HIGHFix: Geta/NestedObjectAssign#11

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

Prototype pollution in nested-object-assign

Also known asGHSA-c497-v8pv-ch6xSNYK-JS-NESTEDOBJECTASSIGN-1065977
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Oct 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs74th percentile — riskier than 74% of all scored CVEsHighest risk
0.00%0.67%1.35%2.02%0.3%1.5%Apr 26Sep 26Oct 26

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

How urgent is this, really

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

12other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
nested-object-assignnpm
52Kdownloads / week

Description

The package nested-object-assign before 1.0.4 are vulnerable to Prototype Pollution via the default function, as demonstrated by running the PoC below.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmnested-object-assignall versions1.0.4npm install nested-object-assign@1.0.4

Affected Products

1 product · 1 configurations
Application
nested-object-assigngetadigital
< 1.0.4
range
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.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nested-object-assign, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

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

The package nested-object-assign before 1.0.4 are vulnerable to Prototype Pollution via the default function, as demonstrated by running the PoC below.
O3 Security · Impact-Aware SCA

Is CVE-2021-23329 in your dependencies?

Find it across npm, including transitive dependencies.

CVE-2021-23329: nested-object-assign — Fixed in 1.0.4