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