High

assign-deep Vulnerable to Prototype Pollution

Disclosed: 21.08.2019
Updated: 11.10.2026 10:22

Versions of assign-deep prior to 1.0.1 and 0.4.8 are vulnerable to Prototype Pollution. The assign function fails to validate which Object properties it updates. This allows attackers to modify the prototype of Object, causing the addition or modification of an existing property on all objects.

Recommendation

Upgrade to versions 1.0.1, 0.4.8, or later.

Affected software

Click a technology to see all vulnerabilities affecting it.

Platform	Package	Vulnerable versions	Fixed in
npm package	assign-deep	< 0.4.8, >= 1.0.0, < 1.0.1	0.4.8, 1.0.1

References

CVSS score 7.5/10

CVSS vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Weakness (CWE): CWE-1321, CWE-20, CWE-915
Platform: npm
Package: assign-deep
Disclosed: 21.08.2019
Updated: 11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-66rh-8fw6-59q6 - CC BY 4.0

Vulnerability history: assign-deep

All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.

Total entries: 2
First → latest: 07.2018 08.2019
Without a fix: 0
Exploited in attacks: 0

Severity breakdown

High 2

Disclosures per year

2018: 1
2019: 1
2020: 0
2021: 0
2022: 0
2023: 0
2024: 0
2025: 0
2026: 0

21.08.2019

assign-deep Vulnerable to Prototype Pollution this entry

High · 7.5 CVE-2019-10745 < 0.4.8, >= 1.0.0, < 1.0.1 0.4.8, 1.0.1
26.07.2018

Prototype Pollution in assign-deep

High · 8.8 CVE-2018-3720 < 0.4.7 0.4.7

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application