Vulnerability Database · npm · assign-deep · Version
assign-deep 0.4.5
0.4.5 is affected by 2 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 1.0.1.
Critical 0 High 2 Medium 0 Low 0 Unrated 0
-
Released 04 Apr 2016
Status deprecated release
Licence MIT
Also known from other sources 2
Newer releases 15
Database updated 23/Oct/2026
Release and licence data published by the npm registry. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
assign-deep 0.4.5 vulnerabilities
2 vulnerabilities cover assign-deep 0.4.5. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2018-3720: Prototype Pollution in assign-deep | 8.8 high | 0.4.7 | 26 Jul 2018 |
| CVE-2019-10745: Prototype Pollution in assign-deep | 7.5 high | 0.4.8 | 21 Aug 2019 |
Looking for another version, or everything Vulert holds for assign-deep?
Questions
About assign-deep 0.4.5
Is assign-deep 0.4.5 vulnerable?
Yes. 2 vulnerabilities in the Vulert database cover assign-deep 0.4.5: 0 critical, 2 high, 0 medium and 0 low. The upgrade Vulert recommends is 1.0.1, and each entry above names the fixed version to move to.
Which version of assign-deep should I use instead of 0.4.5?
1.0.1 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 0.4.5 the latest release of assign-deep?
No. 0.4.5 was published 04 Apr 2016, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor assign-deep for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the assign-deep version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.