Vulnerability Database · npm · safe-object2 · Version
safe-object2 1.0.1
1.0.1 is affected by 2 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 1 High 1 Medium 0 Low 0 Unrated 0
-
Released 06 May 2019
Licence MIT
Also known from other sources 2
Newer releases 3
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
safe-object2 1.0.1 vulnerabilities
2 vulnerabilities cover safe-object2 1.0.1. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2020-7726: Prototype Pollution in safe-object2 | 9.8 critical | No fix published | 06 May 2021 |
| Prototype Pollution in safe-object2 | N/A high | No fix published | 04 Sep 2020 |
Looking for another version, or everything Vulert holds for safe-object2?
Questions
About safe-object2 1.0.1
Is safe-object2 1.0.1 vulnerable?
Yes. 2 vulnerabilities in the Vulert database cover safe-object2 1.0.1: 1 critical, 1 high, 0 medium and 0 low. Each entry above names the fixed version to move to.
Is 1.0.1 the latest release of safe-object2?
No. 1.0.1 was published 06 May 2019, 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 safe-object2 for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the safe-object2 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.