VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

uwsgi: vulnerability history, versions and safety

uwsgi is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 56 releases, from Feb 2018 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H2 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all uwsgi vulnerabilities

Vulert verdict on uwsgi 2.0.31 i

Updated on 23 Oct 2026

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

Package health score 84/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Not enough data

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

  • Current release 2.0.31 — unaffected i
  • Vulnerabilities on record 4 over 8 years · 1 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 142 packages i
  • Last release 12 months ago i
  • Licence GPL-2.0 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 uwsgi, 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.0.31 11 Oct 2025 none GPL-2.0 — Details →
2.0.30 03 Jun 2025 none GPL-2.0 — Details →
2.0.29 11 Apr 2025 none GPL-2.0 — Details →
2.0.28 26 Oct 2024 none GPL-2.0 — Details →
2.0.27 23 Sep 2024 none GPL-2.0 — Details →
2.0.26 01 Jun 2024 none GPL-2.0 — Details →
2.0.25.1 15 Apr 2024 none GPL-2.0 — Details →
2.0.25 13 Apr 2024 none GPL-2.0 — Details →
2.0.24 08 Feb 2024 none GPL-2.0 — Details →
2.0.23 01 Nov 2023 none GPL-2.0 — Details →
2.0.22 27 Jul 2023 none GPL-2.0 — Details →
2.0.21 24 Oct 2022 H1 U1 GPL-2.0 Yes Details →
2.0.20 06 Oct 2021 H1 U1 GPL-2.0 Yes Details →
2.0.19.1 17 Jun 2020 H1 U1 — Yes Details →
2.0.19 14 Jun 2020 H1 U1 — Yes Details →
2.0.18 09 Feb 2019 H1 U1 GPL-2.0 Yes Details →
2.0.17.1 08 Jul 2018 H1 U1 GPL-2.0 Yes Details →
2.0.17 26 Feb 2018 H1 U1 GPL-2.0 Yes Details →
2.0.16 10 Feb 2018 H2 U2 GPL-2.0 Yes Details →
2.0.15 30 Mar 2017 H2 U2 GPL-2.0 Yes Details →
2.0.14 03 Oct 2016 H2 U2 — Yes Details →
2.0.13.1 12 May 2016 H2 U2 — Yes Details →
2.0.13 10 May 2016 H2 U2 — Yes Details →
2.0.12 30 Dec 2015 H2 U2 — Yes Details →
2.0.11.2 07 Oct 2015 H2 U2 — Yes Details →
2.0.11.1 19 Jul 2015 H2 U2 — Yes Details →
2.0.11 01 Jul 2015 H2 U2 — Yes Details →
2.0.10 17 Mar 2015 H2 U2 — Yes Details →
2.0.9 30 Dec 2014 H2 U2 — Yes Details →
2.0.8 27 Oct 2014 H2 U2 — Yes Details →
2.0.7 05 Sep 2014 H2 U2 — Yes Details →
2.0.6 01 Jul 2014 H2 U2 — Yes Details →
2.0.5.1 02 Jun 2014 H2 U2 — Yes Details →
2.0.5 01 Jun 2014 H2 U2 — Yes Details →
2.0.4 22 Apr 2014 H2 U2 — Yes Details →
2.0.3 17 Mar 2014 H2 U2 — Yes Details →
2.0.2 26 Feb 2014 H2 U2 — Yes Details →
2.0.1 09 Feb 2014 H2 U2 — Yes Details →
2.0.0 30 Dec 2013 H2 U2 — Yes Details →
1.9.21.1 12 Dec 2013 H2 U2 — Yes Details →
1.9.21 11 Dec 2013 H2 U2 — Yes Details →
1.9.20 17 Nov 2013 H2 U2 — Yes Details →
1.9.19 09 Nov 2013 H2 U2 — Yes Details →
1.9.18.2 17 Oct 2013 H2 U2 — Yes Details →
1.9.18.1 11 Oct 2013 H2 U2 — Yes Details →
1.9.18 11 Oct 2013 H2 U2 — Yes Details →
1.9.17.1 24 Sep 2013 H2 U2 — Yes Details →
1.9.17 22 Sep 2013 H2 U2 — Yes Details →
1.9.16 14 Sep 2013 H2 U2 — Yes Details →
1.9.15 29 Aug 2013 H2 U2 — Yes Details →
1.4.10 23 Aug 2013 H2 U2 — Yes Details →
1.9.14 21 Jul 2013 H2 U2 — Yes Details →
1.9.13 22 Jun 2013 H2 U2 — Yes Details →
1.9.12 05 Jun 2013 H2 U2 — Yes Details →
1.9.11 26 May 2013 H2 U2 — Yes Details →
1.9.10 11 May 2013 H2 U2 — Yes Details →
1.9.9 08 May 2013 H2 U2 — Yes Details →
1.9.8 23 Apr 2013 H2 U2 — Yes Details →
1.9.7 22 Apr 2013 H2 U2 — Yes Details →
1.9.6 09 Apr 2013 H2 U2 — Yes Details →
1.9.5 04 Apr 2013 H2 U2 — Yes Details →
1.9.4 30 Mar 2013 H2 U2 — Yes Details →
1.9.3 28 Mar 2013 H2 U2 — Yes Details →
1.9.2 26 Mar 2013 H2 U2 — Yes Details →
1.9.1 24 Mar 2013 H2 U2 — Yes Details →
1.9.0 17 Mar 2013 H2 U2 — Yes Details →
1.4.9 17 Mar 2013 H2 U2 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2022 1
  • 2023 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for uwsgi

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-27522: Apache HTTP Server via mod_proxy_uwsgi HTTP response smuggling 7.5 high 2.0.22 07 Mar 2023
uWSGI Directory Traversal Vulnerability in uwsgi 7.5 high 2.0.17 14 May 2022
CVE-2023-27522: uwsgi Package Vulnerability in Apache HTTP Server Leading to HTTP Response Smuggling 7.5 high 2.0.22 07 Jul 2026
CVE-2018-7490: uWSGI Directory Traversal Vulnerability N/A unrated 2.0.17 26 Feb 2018

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 uwsgi

Is uwsgi safe to use?

Vulert records 4 vulnerabilities for uwsgi in PyPI: 0 critical, 2 high, 0 medium and 0 low, plus 2 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 uwsgi's Vulert package health score?

Vulert scores uwsgi 84/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 uwsgi affected?

No. 2.0.31, 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 uwsgi should I use?

2.0.31 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 uwsgi have?

4 vulnerabilities are recorded for uwsgi in the PyPI ecosystem: 0 critical, 2 high, 0 medium and 0 low, plus 2 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 uwsgi vulnerabilities disclosed?

1 vulnerability was recorded for uwsgi in the last 12 months, and the oldest entry in this database dates to 26 Feb 2018. 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 uwsgi 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 uwsgi for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the uwsgi version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.