Vulnerability Database · npm · public · Version
public 0.1.1
0.1.1 is affected by 5 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 0.1.5.
Critical 0 High 1 Medium 3 Low 1 Unrated 0
-
Released 22 Nov 2011
Status deprecated release
Also known from other sources 5
Newer releases 6
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
public 0.1.1 vulnerabilities
5 vulnerabilities cover public 0.1.1. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2018-3731: Path Traversal in public | 7.5 high | 0.1.3 | 18 Jul 2018 |
| CVE-2018-16480: XSS Vulnerability in public | 6.1 medium | 0.1.4 | 07 Feb 2019 |
| CVE-2018-3747: Cross-Site Scripting in public | 6.1 medium | 0.1.4 | 10 Oct 2018 |
| Path Traversal Vulnerability in public npm package | N/A medium | No fix published | 03 Sep 2020 |
| Cross-Site Scripting Vulnerability in public Package | N/A low | 0.1.4 | 31 May 2019 |
Looking for another version, or everything Vulert holds for public?
Questions
About public 0.1.1
Is public 0.1.1 vulnerable?
Yes. 5 vulnerabilities in the Vulert database cover public 0.1.1: 0 critical, 1 high, 3 medium and 1 low. The upgrade Vulert recommends is 0.1.5, and each entry above names the fixed version to move to.
Which version of public should I use instead of 0.1.1?
0.1.5 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.1.1 the latest release of public?
No. 0.1.1 was published 22 Nov 2011, 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 public for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the public version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.