VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

mitogen: vulnerability history, versions and safety

mitogen is a package in the PyPI ecosystem. Vulert records 3 vulnerabilities for it across 71 releases, first recorded in Aug 2019. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded C1 U2
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 mitogen vulnerabilities

Vulert verdict on mitogen 0.3.54 i

Updated on 23 Oct 2026

Action needed: 0.3.54 has 2 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 75/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 0.3.54 — affected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 19 Aug 2019 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 20 packages i
  • Stars 2,545 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence BSD-3-Clause 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 mitogen, 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
0.3.54 07 Oct 2026 U2 BSD-3-Clause Yes Details →
0.3.53 01 Sep 2026 U2 BSD-3-Clause Yes Details →
0.3.52 25 Aug 2026 U2 BSD-3-Clause Yes Details →
0.3.51 18 Jul 2026 U2 BSD-3-Clause Yes Details →
0.3.50 19 Jun 2026 U2 BSD-3-Clause Yes Details →
0.3.49 03 Jun 2026 U2 BSD-3-Clause Yes Details →
0.3.48 22 May 2026 U2 BSD-3-Clause Yes Details →
0.3.47 19 Apr 2026 U2 BSD-3-Clause Yes Details →
0.3.46 16 Apr 2026 U2 BSD-3-Clause Yes Details →
0.3.45 30 Mar 2026 U2 BSD-3-Clause Yes Details →
0.3.44 15 Mar 2026 U2 BSD-3-Clause Yes Details →
0.3.43 02 Mar 2026 U2 BSD-3-Clause Yes Details →
0.3.42 20 Feb 2026 U2 BSD-3-Clause Yes Details →
0.3.41 10 Feb 2026 U2 BSD-3-Clause Yes Details →
0.3.40 04 Feb 2026 U2 BSD-3-Clause Yes Details →
0.3.39 27 Jan 2026 U2 BSD-3-Clause Yes Details →
0.3.38 23 Jan 2026 U2 BSD-3-Clause Yes Details →
0.3.37 08 Jan 2026 U2 BSD-3-Clause Yes Details →
0.3.36 18 Dec 2025 U2 BSD-3-Clause Yes Details →
0.3.35 01 Dec 2025 U2 BSD-3-Clause Yes Details →
0.3.34 27 Nov 2025 U2 BSD-3-Clause Yes Details →
0.3.33 22 Nov 2025 U2 BSD-3-Clause Yes Details →
0.3.32 21 Nov 2025 U2 BSD-3-Clause Yes Details →
0.3.31 05 Nov 2025 U2 BSD-3-Clause Yes Details →
0.3.30 30 Oct 2025 U2 BSD-3-Clause Yes Details →
0.3.29 18 Sep 2025 U2 non-standard Yes Details →
0.3.28 17 Sep 2025 U2 non-standard Yes Details →
0.3.27 20 Aug 2025 U2 non-standard Yes Details →
0.3.26 04 Aug 2025 U2 non-standard Yes Details →
0.3.25 29 Jul 2025 U2 non-standard Yes Details →
0.3.25b1 21 Jul 2025 U2 non-standard Yes Details →
0.3.25a3 02 Jul 2025 U2 non-standard Yes Details →
0.3.25a2 21 Jun 2025 U2 non-standard Yes Details →
0.3.25a1 04 Jun 2025 U2 non-standard Yes Details →
0.3.24 29 May 2025 U2 non-standard Yes Details →
0.3.23 28 Apr 2025 U2 non-standard Yes Details →
0.3.22 04 Feb 2025 U2 non-standard Yes Details →
0.3.21 20 Jan 2025 U2 non-standard Yes Details →
0.3.20 07 Jan 2025 U2 non-standard Yes Details →
0.3.19 02 Dec 2024 U2 non-standard Yes Details →
0.3.18 07 Nov 2024 U2 non-standard Yes Details →
0.3.17 07 Nov 2024 U2 non-standard Yes Details →
0.3.16 05 Nov 2024 U2 non-standard Yes Details →
0.3.15 28 Oct 2024 U2 non-standard Yes Details →
0.3.14 16 Oct 2024 U2 non-standard Yes Details →
0.3.13 09 Oct 2024 U2 non-standard Yes Details →
0.3.12 07 Oct 2024 U2 non-standard Yes Details →
0.3.11 30 Sep 2024 U2 non-standard Yes Details →
0.3.10 20 Sep 2024 U2 non-standard Yes Details →
0.3.9 13 Aug 2024 U2 non-standard Yes Details →
0.3.8 30 Jul 2024 U2 non-standard Yes Details →
0.3.7 09 Apr 2024 U2 non-standard Yes Details →
0.3.6 04 Apr 2024 U2 non-standard Yes Details →
0.3.5 28 Mar 2024 U2 non-standard Yes Details →
0.3.4 02 Jul 2023 U2 non-standard Yes Details →
0.3.3 12 Jun 2022 U2 non-standard Yes Details →
0.3.2 15 Jan 2022 U2 non-standard Yes Details →
0.3.0 28 Oct 2021 U2 non-standard Yes Details →
0.2.10 28 Oct 2021 U2 non-standard Yes Details →
0.3.0rc1 31 Jan 2021 U2 non-standard Yes Details →
0.2.10rc1 31 Jan 2021 U2 non-standard Yes Details →
0.2.9 02 Nov 2019 U2 non-standard Yes Details →
0.2.8 18 Aug 2019 U2 non-standard Yes Details →
0.2.7 19 May 2019 C1 U2 non-standard Yes Details →
0.2.6 06 Mar 2019 C1 U2 non-standard Yes Details →
0.2.5 14 Feb 2019 C1 U2 non-standard Yes Details →
0.2.4 10 Feb 2019 C1 U2 non-standard Yes Details →
0.2.3 23 Oct 2018 C1 U2 non-standard Yes Details →
0.2.2 27 Jul 2018 C1 U2 non-standard Yes Details →
0.2.1 10 Jul 2018 C1 U2 non-standard Yes Details →
0.2.0 09 Jul 2018 C1 U2 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 3

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

03 Vulnerabilities

Recorded vulnerabilities for mitogen

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-15149: Mitogen core.py Unidirectional-Routing Protection Bypass 9.8 critical 0.2.8 19 Aug 2019
CVE-2019-15149: Mitogen Unidirectional-Routing Protection Bypass N/A unrated 5924af1566763e48c42028399ea0cd95c457b3dc 18 Aug 2019
CVE-2019-15149: Mitogen core.py Unidirectional-Routing Protection Bypass N/A unrated 5924af1566763e48c42028399ea0cd95c457b3dc 18 Aug 2019

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 mitogen

Is mitogen safe to use?

Vulert records 3 vulnerabilities for mitogen in PyPI: 1 critical, 0 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 mitogen's Vulert package health score?

Vulert scores mitogen 75/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 mitogen affected?

Yes. 0.3.54, the version you would install today, has 2 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of mitogen should I use?

0.3.54 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 mitogen have?

3 vulnerabilities are recorded for mitogen in the PyPI ecosystem: 1 critical, 0 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 mitogen vulnerabilities disclosed?

0 vulnerabilities were recorded for mitogen in the last 12 months, and the oldest entry in this database dates to 18 Aug 2019. 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 mitogen 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 mitogen for upcoming vulnerabilities?

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