VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

moin: vulnerability history, versions and safety

moin is a package in the PyPI ecosystem. Vulert records 82 vulnerabilities for it across 22 releases, from Apr 2008 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
82 vulnerabilities recorded H11 M30 U41
i
12 with no fix published

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

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

Most recent disclosure 02 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all moin vulnerabilities

Vulert verdict on moin 1.9.11 i

Updated on 23 Oct 2026

Careful: 1.9.11 has 14 known vulnerabilities, and 12 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 32/100
  • Security Unfixed issues
  • Maintenance Slowing
  • Popularity Niche
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 1.9.11 — affected i
  • Vulnerabilities on record 82 over 18 years · 14 in the last year i
  • Latest disclosure 02 Jul 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 12 i
  • Depended on by 1 packages i
  • Stars 374 i
  • Last release 71 months ago i
  • Licence GPL-2.0-or-later 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 moin, 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.0b5 24 Mar 2026 M7 U7 GPL-2.0-or-later No Details →
2.0.0b4 07 Nov 2025 M7 U7 GPL-2.0-or-later No Details →
2.0.0b3 24 May 2025 M7 U7 non-standard No Details →
2.0.0b2 02 Mar 2025 M7 U7 non-standard No Details →
2.0.0b1 06 Aug 2024 M7 U7 non-standard No Details →
2.0.0a1 27 Mar 2024 M7 U7 non-standard No Details →
1.9.11 08 Nov 2020 U1 non-standard No Details →
1.9.10 09 Sep 2018 H1 M1 U3 non-standard No Details →
1.9.9 31 Oct 2016 H1 M2 U4 non-standard No Details →
1.9.7 05 Oct 2015 H1 M4 U7 non-standard No Details →
1.9.6 05 Oct 2015 H1 M4 U7 non-standard No Details →
1.9.5 05 Oct 2015 H1 M8 U11 non-standard No Details →
1.9.4 05 Oct 2015 H1 M9 U12 non-standard No Details →
1.9.3 05 Oct 2015 H1 M9 U12 non-standard No Details →
1.9.2 05 Oct 2015 H1 M11 U16 non-standard No Details →
1.9.1 05 Oct 2015 H1 M11 U18 non-standard No Details →
1.9.0 05 Oct 2015 H2 M11 U19 non-standard No Details →
1.8.7 05 Oct 2015 H1 M8 U13 non-standard No Details →
1.8.6 05 Oct 2015 H3 M9 U16 non-standard No Details →
1.8.5 05 Oct 2015 H3 M9 U16 non-standard No Details →
1.8.4 05 Oct 2015 H3 M9 U16 non-standard No Details →
1.9.8 17 Oct 2014 H1 M4 U6 non-standard No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2008 2
  • 2009 4
  • 2010 9
  • 2011 1
  • 2012 1
  • 2013 4
  • 2016 2
  • 2017 1
  • 2018 1
  • 2019 1
  • 2020 4
  • 2022 38
  • 2026 14

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

03 Vulnerabilities

Recorded vulnerabilities for moin

The 5 most severe of 82 vulnerabilities recorded for this package

Search all 82 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-25074: Remote Code Execution via Cache Action in MoinMoin 8.8 high 1.9.11 11 Nov 2020
CVE-2020-15275: MoinMoin Wiki - Malicious SVG Attachment Stored XSS Vulnerability 8.7 medium 1.9.11 11 Nov 2020
CVE-2008-1937: MoinMoin Privilege Escalation 7.5 high 1.6.3 01 May 2022
CVE-2008-6603: MoinMoin Access Restrictions Bypassed due to improper ACL enforcement 7.5 high 1.6.3 17 May 2022
CVE-2008-6549: MoinMoin Denial of Service vulnerability via password_checker function 7.5 high 1.6.1 17 May 2022

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 moin

Is moin safe to use?

Vulert records 82 vulnerabilities for moin in PyPI: 0 critical, 11 high, 30 medium and 0 low, plus 41 not yet rated. 12 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is moin's Vulert package health score?

Vulert scores moin 32/100, which reads as risky. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of moin affected?

Yes. 1.9.11, the version you would install today, has 14 known vulnerabilities, and 12 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of moin should I use?

1.9.11 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 moin have?

82 vulnerabilities are recorded for moin in the PyPI ecosystem: 0 critical, 11 high, 30 medium and 0 low, plus 41 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 moin vulnerabilities disclosed?

14 vulnerabilities were recorded for moin in the last 12 months, and the oldest entry in this database dates to 25 Apr 2008. 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 moin 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 moin for upcoming vulnerabilities?

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