VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

proxy-py: vulnerability history, versions and safety

proxy-py is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 10 releases, from Jan 2021 to Apr 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all proxy-py vulnerabilities

Vulert verdict on proxy-py 2.4.10 i

Updated on 23 Oct 2026

Good news: 2.4.10, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 73/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Moderate

What to do: Stay on 2.4.10 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.4.10 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.4.10 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 07 Apr 2021 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 17 packages i
  • Stars 3,557 i
  • OpenSSF scorecard 3/10 i
  • Last release 20 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for proxy-py, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.4.10 18 Feb 2025 none non-standard — Details →
2.4.9 14 Oct 2024 none non-standard — Details →
2.4.8 22 Sep 2024 none non-standard — Details →
2.4.7 13 Aug 2024 none non-standard — Details →
2.4.5 06 Aug 2024 none non-standard — Details →
2.4.4 10 May 2024 none non-standard — Details →
2.4.4rc5 12 Apr 2024 none non-standard — Details →
2.4.4rc4 14 Mar 2023 none non-standard — Details →
2.4.4rc3 13 Aug 2022 none non-standard — Details →
2.4.4rc2 01 Aug 2022 none non-standard — Details →
2.4.4rc1 28 Jun 2022 none non-standard — Details →
2.4.3 12 Jun 2022 none non-standard — Details →
2.4.2 23 May 2022 none non-standard — Details →
2.4.1 13 Mar 2022 none non-standard — Details →
2.4.0 03 Feb 2022 none non-standard — Details →
2.4.0rc9 26 Jan 2022 none non-standard — Details →
2.4.0rc8 24 Jan 2022 none non-standard — Details →
2.4.0rc7 20 Jan 2022 none non-standard — Details →
2.4.0a7 20 Jan 2022 none non-standard — Details →
2.4.0rc6 14 Jan 2022 none non-standard — Details →
2.4.0b6 14 Jan 2022 none non-standard — Details →
2.4.0a6 11 Jan 2022 none non-standard — Details →
2.4.0rc5 01 Jan 2022 none non-standard — Details →
2.4.0a5 01 Jan 2022 none non-standard — Details →
2.4.0rc4 21 Dec 2021 none non-standard — Details →
2.4.0rc3 19 Dec 2021 none non-standard — Details →
2.4.0b3 18 Dec 2021 none non-standard — Details →
2.4.0b2 17 Dec 2021 none non-standard — Details →
2.4.0rc2 01 Dec 2021 none non-standard — Details →
2.4.0b1 01 Dec 2021 none non-standard — Details →
2.4.0rc1 28 Nov 2021 none non-standard — Details →
2.4.0a2 28 Nov 2021 none non-standard — Details →
2.4.0a1 28 Nov 2021 none non-standard — Details →
2.3.1 10 Jan 2021 none non-standard — Details →
2.2.0 17 Jun 2020 H1 U1 non-standard Yes Details →
2.1.2 31 Jan 2020 H1 U1 non-standard Yes Details →
2.1.1 31 Jan 2020 H1 U1 non-standard Yes Details →
2.0.0 26 Dec 2019 H1 U1 non-standard Yes Details →
1.1.1 10 Oct 2019 H1 U1 non-standard Yes Details →
1.1.0 10 Oct 2019 H1 U1 non-standard Yes Details →
1.0.0 27 Sep 2019 H1 U1 non-standard Yes Details →
0.3.0 09 Feb 2019 H1 U1 non-standard Yes Details →
0.2.0 17 Mar 2015 H1 U1 non-standard Yes Details →
0.1.0 31 Aug 2013 H1 U1 non-standard Yes Details →

All 44 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for proxy-py

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 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

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About proxy-py

Is proxy-py safe to use?

Vulert records 2 vulnerabilities for proxy-py in PyPI: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is proxy-py's Vulert package health score?

Vulert scores proxy-py 73/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of proxy-py affected?

No. 2.4.10, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of proxy-py should I use?

2.4.10 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does proxy-py have?

2 vulnerabilities are recorded for proxy-py in the PyPI ecosystem: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new proxy-py vulnerabilities disclosed?

0 vulnerabilities were recorded for proxy-py in the last 12 months, and the oldest entry in this database dates to 11 Jan 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of proxy-py are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

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.