Vulnerability Database · npm · multi-ini · Version
multi-ini 2.1.0
2.1.0 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: 2.3.2.
Critical 1 High 0 Medium 1 Low 0 Unrated 0
-
Released 23 Feb 2020
Licence MIT
Also known from other sources 2
Newer releases 23
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
multi-ini 2.1.0 vulnerabilities
2 vulnerabilities cover multi-ini 2.1.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2020-28448: Prototype Pollution in multi-ini | 9.8 critical | 2.1.1 | 13 Apr 2021 |
| CVE-2020-28460: Prototype Pollution in multi-ini | 5.6 medium | 2.1.2 | 13 Apr 2021 |
Looking for another version, or everything Vulert holds for multi-ini?
Questions
About multi-ini 2.1.0
Is multi-ini 2.1.0 vulnerable?
Yes. 2 vulnerabilities in the Vulert database cover multi-ini 2.1.0: 1 critical, 0 high, 1 medium and 0 low. The upgrade Vulert recommends is 2.3.2, and each entry above names the fixed version to move to.
Which version of multi-ini should I use instead of 2.1.0?
2.3.2 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 2.1.0 the latest release of multi-ini?
No. 2.1.0 was published 23 Feb 2020, 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 multi-ini for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the multi-ini version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.