Vulnerability Database · PyPI · proxy-py · Version
proxy-py 0.1.0
0.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.4.10.
Critical 0 High 1 Medium 0 Low 0 Unrated 1
-
Released 31 Aug 2013
Licence non-standard
Also known from other sources 2
Newer releases 44
Database updated 23/Oct/2026
Release and licence data published by PyPI. 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
proxy-py 0.1.0 vulnerabilities
2 vulnerabilities cover proxy-py 0.1.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2021-3116: Logic error in authentication in proxy.py | 7.5 high | 2.3.1 | 07 Apr 2021 |
| CVE-2021-3116: Proxy-py - Incorrect Proxy-Authorization Header Data | N/A unrated | 2.3.1 | 11 Jan 2021 |
Looking for another version, or everything Vulert holds for proxy-py?
Questions
About proxy-py 0.1.0
Is proxy-py 0.1.0 vulnerable?
Yes. 2 vulnerabilities in the Vulert database cover proxy-py 0.1.0: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. The upgrade Vulert recommends is 2.4.10, and each entry above names the fixed version to move to.
Which version of proxy-py should I use instead of 0.1.0?
2.4.10 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.0 the latest release of proxy-py?
No. 0.1.0 was published 31 Aug 2013, 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 proxy-py for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the proxy-py version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.