Vulnerability Database · npm · tiny-conf · Version
tiny-conf 1.0.1
1.0.1 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 06 Sep 2016
Licence MIT
Also known from other sources 1
Newer releases 7
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
tiny-conf 1.0.1 vulnerabilities
1 vulnerability cover tiny-conf 1.0.1. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2020-7724: Prototype Pollution in tiny-conf | 9.8 critical | No fix published | 10 May 2021 |
Looking for another version, or everything Vulert holds for tiny-conf?
Questions
About tiny-conf 1.0.1
Is tiny-conf 1.0.1 vulnerable?
Yes. 1 vulnerability in the Vulert database cover tiny-conf 1.0.1: 1 critical, 0 high, 0 medium and 0 low. Each entry above names the fixed version to move to.
Is 1.0.1 the latest release of tiny-conf?
No. 1.0.1 was published 06 Sep 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 tiny-conf for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the tiny-conf version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.