VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

mitmproxy: vulnerability history, versions and safety

mitmproxy is a package in the PyPI ecosystem. Vulert records 11 vulnerabilities for it across 86 releases, from Jul 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
11 vulnerabilities recorded C3 H1 M2 U5
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 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 mitmproxy vulnerabilities

Vulert verdict on mitmproxy 12.3.0 i

Updated on 23 Oct 2026

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

Package health score 79/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 12.3.0 — unaffected i
  • Vulnerabilities on record 11 over 7 years · 3 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Stars 45,806 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence non-standard i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 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 mitmproxy, 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
12.3.0 22 Oct 2026 none non-standard — Details →
12.2.3 12 May 2026 none non-standard — Details →
12.2.2 12 Apr 2026 none non-standard — Details →
12.2.1 24 Nov 2025 M1 U1 non-standard Yes Details →
12.2.0 15 Oct 2025 M1 U1 non-standard Yes Details →
12.1.2 24 Aug 2025 M1 U1 non-standard Yes Details →
12.1.1 25 May 2025 M2 U1 non-standard Yes Details →
12.1.0 24 May 2025 M2 U1 non-standard Yes Details →
12.0.1 06 May 2025 M2 U1 non-standard Yes Details →
12.0.0 29 Apr 2025 M2 U1 non-standard Yes Details →
11.1.3 17 Feb 2025 M2 U1 non-standard Yes Details →
11.1.2 06 Feb 2025 M2 U1 non-standard Yes Details →
11.1.0 12 Jan 2025 H1 M2 U2 non-standard Yes Details →
11.0.2 05 Dec 2024 H1 M2 U2 non-standard Yes Details →
11.0.1 24 Nov 2024 H1 M2 U2 non-standard Yes Details →
11.0.0 02 Oct 2024 H1 M2 U2 non-standard Yes Details →
10.4.2 02 Aug 2024 H1 M2 U2 non-standard Yes Details →
10.4.1 29 Jul 2024 H1 M2 U2 non-standard Yes Details →
10.4.0 25 Jul 2024 H1 M2 U2 non-standard Yes Details →
10.3.1 12 Jun 2024 H1 M2 U2 non-standard Yes Details →
10.3.0 17 Apr 2024 H1 M2 U2 non-standard Yes Details →
10.2.4 07 Mar 2024 H1 M2 U2 non-standard Yes Details →
10.2.3 06 Mar 2024 H1 M2 U2 non-standard Yes Details →
10.2.2 21 Jan 2024 H1 M2 U2 non-standard Yes Details →
10.2.1 06 Jan 2024 H1 M2 U2 non-standard Yes Details →
10.2.0 04 Jan 2024 H1 M2 U2 non-standard Yes Details →
10.1.6 14 Dec 2023 H1 M2 U2 non-standard Yes Details →
10.1.5 14 Nov 2023 H1 M2 U2 non-standard Yes Details →
10.1.4 13 Nov 2023 H1 M2 U2 non-standard Yes Details →
10.1.3 04 Nov 2023 H1 M2 U2 non-standard Yes Details →
10.1.2 03 Nov 2023 H1 M2 U2 non-standard Yes Details →
10.1.1 27 Sep 2023 H1 M2 U2 non-standard Yes Details →
10.1.0 24 Sep 2023 H1 M2 U2 non-standard Yes Details →
10.0.0 04 Aug 2023 H1 M2 U2 non-standard Yes Details →
9.0.1 02 Nov 2022 H1 M2 U2 MIT Yes Details →
9.0.0 28 Oct 2022 H1 M2 U2 MIT Yes Details →
8.1.1 28 Jun 2022 H1 M2 U2 MIT Yes Details →
8.1.0 15 May 2022 H1 M2 U2 MIT Yes Details →
8.0.0 19 Mar 2022 H1 M2 U2 MIT Yes Details →
7.0.4 28 Sep 2021 C1 H1 M2 U3 MIT Yes Details →
7.0.3 16 Sep 2021 C1 H1 M2 U3 MIT Yes Details →
7.0.2 04 Aug 2021 C2 H1 M2 U4 MIT Yes Details →
7.0.1 03 Aug 2021 C2 H1 M2 U4 MIT Yes Details →
7.0.0 16 Jul 2021 C2 H1 M2 U4 MIT Yes Details →
6.0.2 15 Dec 2020 C2 H1 M2 U4 MIT Yes Details →
6.0.1 13 Dec 2020 C2 H1 M2 U4 MIT Yes Details →
6.0.0 12 Dec 2020 C2 H1 M2 U4 MIT Yes Details →
5.3.0 01 Nov 2020 C2 H1 M2 U4 MIT Yes Details →
5.2.0 18 Jul 2020 C2 H1 M2 U3 MIT Yes Details →
5.1.1 13 Apr 2020 C2 H1 M2 U4 MIT Yes Details →
5.1.0 13 Apr 2020 C2 H1 M2 U4 MIT Yes Details →
5.0.1 27 Dec 2019 C2 H1 M2 U4 MIT Yes Details →
5.0.0 16 Dec 2019 C2 H1 M2 U4 MIT Yes Details →
4.0.4 31 Jul 2018 C2 H1 M2 U4 MIT Yes Details →
4.0.3 16 Jun 2018 C3 H1 M2 U5 MIT Yes Details →
4.0.1 17 May 2018 C3 H1 M2 U5 MIT Yes Details →
4.0.0 17 May 2018 C3 H1 M2 U5 MIT Yes Details →
3.0.4 05 Apr 2018 C3 H1 M2 U5 MIT Yes Details →
3.0.3 25 Feb 2018 C3 H1 M2 U5 MIT Yes Details →
3.0.2 23 Feb 2018 C3 H1 M2 U5 MIT Yes Details →
3.0.1 23 Feb 2018 C3 H1 M2 U5 MIT Yes Details →
3.0.0 22 Feb 2018 C3 H1 M2 U5 MIT Yes Details →
2.0.2 28 Apr 2017 C3 H1 M2 U5 MIT Yes Details →
2.0.1 15 Mar 2017 C3 H1 M2 U5 MIT Yes Details →
2.0.0 21 Feb 2017 C3 H1 M2 U5 MIT Yes Details →
1.0.2 07 Jan 2017 C3 H1 M2 U5 MIT Yes Details →
1.0.1 27 Dec 2016 C3 H1 M2 U5 MIT Yes Details →
0.18.3 27 Dec 2016 C3 H1 M2 U5 MIT Yes Details →
1.0.0 26 Dec 2016 C3 H1 M2 U5 MIT Yes Details →
0.18.2 26 Oct 2016 C3 H1 M2 U5 MIT Yes Details →
0.18.1 16 Oct 2016 C3 H1 M2 U5 MIT Yes Details →
0.15.0 03 Dec 2015 C3 H1 M2 U4 MIT Yes Details →
0.14.0 06 Nov 2015 C3 H1 M2 U5 MIT Yes Details →
0.13.0 21 Jul 2015 C3 H1 M2 U4 MIT Yes Details →
0.12.1 03 Jun 2015 C3 H1 M2 U5 MIT Yes Details →
0.12.0 25 May 2015 C3 H1 M2 U5 MIT Yes Details →
0.11.3 29 Dec 2014 C3 H1 M2 U5 MIT Yes Details →
0.11.2 28 Dec 2014 C3 H1 M2 U5 MIT Yes Details →
0.11.1 15 Nov 2014 C3 H1 M2 U5 MIT Yes Details →
0.11.0 11 Nov 2014 C3 H1 M2 U4 MIT Yes Details →
0.10.1 26 Feb 2014 C3 H1 M2 U5 MIT Yes Details →
0.10.0 28 Jan 2014 C3 H1 M2 U4 MIT Yes Details →
0.9.2 24 Aug 2013 C3 H1 M2 U5 MIT Yes Details →
0.9.1 16 Jun 2013 C3 H1 M2 U5 MIT Yes Details →
0.9.0 14 May 2013 C3 H1 M2 U4 non-standard Yes Details →
0.8.1 17 Nov 2012 C3 H1 M2 U5 non-standard Yes Details →
0.8.0 09 Apr 2012 C3 H1 M2 U4 non-standard Yes Details →
0.16.0 — C3 H1 M2 U4 — Yes Details →
0.17.0 — C3 H1 M2 U4 — Yes Details →

All 89 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 2
  • 2021 2
  • 2022 2
  • 2025 2
  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for mitmproxy

The 5 most severe of 11 vulnerabilities recorded for this package

Search all 11 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-24766: Insufficient Protection against HTTP Request Smuggling in mitmproxy 9.8 critical 8.0.0 22 Mar 2022
CVE-2018-14505: Mitmweb in mitmproxy allows DNS Rebinding attacks 8.8 critical 4.0.4 31 Jul 2018
CVE-2025-23217: mitmproxy API Authentication Bypass Vulnerability 8.2 high 11.1.2 06 Feb 2025
CVE-2025-23217: mitmproxy API Authentication Bypass Vulnerability 8.2 high 11.1.2 07 Jul 2026
CVE-2021-39214: Lacking Protection against HTTP Request Smuggling in mitmproxy 8.1 critical 7.0.3 20 Sep 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 mitmproxy

Is mitmproxy safe to use?

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

Vulert scores mitmproxy 79/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 mitmproxy affected?

No. 12.3.0, 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.

How many vulnerabilities does mitmproxy have?

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

3 vulnerabilities were recorded for mitmproxy in the last 12 months, and the oldest entry in this database dates to 22 Jul 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 mitmproxy 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 mitmproxy for upcoming vulnerabilities?

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