VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

mitmproxy: vulnerability history, versions and safety

mitmproxy is a package in the Debian ecosystem. Vulert records 7 vulnerabilities for it across 6 releases, from Jul 2018 to Apr 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
7 vulnerabilities recorded U7
i
5 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 21 Apr 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mitmproxy vulnerabilities

Vulert verdict on mitmproxy i

Updated on 23 Oct 2026

Careful: 5 of the 7 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 7 vulnerabilities on record across 7 years, 1 in the last year.

What to do: Plan around the 5 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 7 over 7 years · 1 in the last year i
  • Latest disclosure 21 Apr 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 5 i

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 holds for mitmproxy, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
8.1.1-4 U1 No Details →
8.1.1-3 U5 No Details →
8.1.1-2 U5 No Details →
8.1.1-1 U5 No Details →
6.0.2-2 U5 No Details →
6.0.2-1 U5 No Details →

Newest 6 of 6 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 2
  • 2021 1
  • 2022 1
  • 2025 2
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for mitmproxy

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
HTTP Request Smuggling Vulnerability in mitmproxy: A Critical Security Flaw 9.8 critical No fix published 16 Sep 2021
HTTP Request Smuggling Vulnerability in mitmproxy: A Critical Security Flaw 9.8 critical No fix published 21 Mar 2022
DNS Rebinding Vulnerability in mitmproxy: CVE-2018-14505 8.8 high 3.0.4-1 22 Jul 2018
Critical SSRF Vulnerability in mitmweb Allows Potential Remote Code Execution N/A unrated No fix published 06 Feb 2025
DNS Rebinding Vulnerability in mitmproxy: A Security Risk for Web Applications N/A unrated 3.0.4-1 22 Jul 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 mitmproxy

Is mitmproxy safe to use?

Vulert records 7 vulnerabilities for mitmproxy in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 7 not yet rated. 5 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does mitmproxy have?

7 vulnerabilities are recorded for mitmproxy in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 7 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?

1 vulnerability was 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.