VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

mesop: vulnerability history, versions and safety

mesop is a package in the PyPI ecosystem. Vulert records 12 vulnerabilities for it across 104 releases, from Sep 2024 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
12 vulnerabilities recorded C2 H3 M1 U6
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
10 in the last 12 months

Most recent disclosure 01 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mesop vulnerabilities

Vulert verdict on mesop 1.3.7 i

Updated on 23 Oct 2026

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

Package health score 58/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

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

  • Current release 1.3.7 — unaffected i
  • Vulnerabilities on record 12 over 2 years · 10 in the last year i
  • Latest disclosure 01 Oct 2026 i
  • Highest CVSS 10.0 i
  • With no published fix 0 i
  • Depended on by 7 packages i
  • Stars 6,582 i
  • Last release this month i
  • Licence Apache-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 mesop, 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
1.3.7 26 Sep 2026 none Apache-2.0 — Details →
1.3.6 18 Sep 2026 none Apache-2.0 — Details →
1.3.5 17 Aug 2026 none Apache-2.0 — Details →
1.3.4 01 Aug 2026 none Apache-2.0 — Details →
1.3.3 11 Jul 2026 M1 U1 Apache-2.0 Yes Details →
1.3.2 07 Jun 2026 M1 U1 Apache-2.0 Yes Details →
1.3.0 13 May 2026 M1 U1 Apache-2.0 Yes Details →
1.3.0rc2 10 May 2026 M1 U1 Apache-2.0 Yes Details →
1.3.0rc1 26 Apr 2026 M1 U1 Apache-2.0 Yes Details →
1.2.7 07 Apr 2026 M1 U1 Apache-2.0 Yes Details →
1.2.7rc1 05 Apr 2026 M1 U1 Apache-2.0 Yes Details →
1.2.6rc2 31 Mar 2026 M1 U1 Apache-2.0 Yes Details →
1.2.5 31 Mar 2026 M1 U1 Apache-2.0 Yes Details →
1.2.5rc1 30 Mar 2026 H1 M1 U2 Apache-2.0 Yes Details →
1.2.4rc1 17 Mar 2026 H1 M1 U2 Apache-2.0 Yes Details →
1.2.3 16 Mar 2026 H1 M1 U2 Apache-2.0 Yes Details →
1.2.2 23 Feb 2026 C2 M1 U3 Apache-2.0 Yes Details →
1.2.2rc1 22 Feb 2026 C2 M1 U3 Apache-2.0 Yes Details →
1.2.1 20 Feb 2026 C2 M1 U3 Apache-2.0 Yes Details →
1.2.1rc1 16 Feb 2026 C2 M1 U3 Apache-2.0 Yes Details →
1.2.0 01 Jan 2026 C2 M1 U3 Apache-2.0 Yes Details →
1.2.0rc1 31 Dec 2025 C2 M1 U3 Apache-2.0 Yes Details →
1.1.1 24 Nov 2025 C2 M1 U3 Apache-2.0 Yes Details →
1.1.1rc3 22 Nov 2025 C2 M1 U3 Apache-2.0 Yes Details →
1.1.1rc2 20 Nov 2025 C2 M1 U3 Apache-2.0 Yes Details →
1.1.1rc1 20 Nov 2025 C2 M1 U3 Apache-2.0 Yes Details →
1.1.0 19 Jun 2025 C2 M1 U3 Apache-2.0 Yes Details →
1.1.0rc1 19 Jun 2025 C2 M1 U3 Apache-2.0 Yes Details →
1.0.1 01 Apr 2025 C2 M1 U3 Apache-2.0 Yes Details →
1.0.1rc1 01 Apr 2025 C2 M1 U3 Apache-2.0 Yes Details →
1.0.0 19 Mar 2025 C2 M1 U3 Apache-2.0 Yes Details →
1.0.0rc2 19 Mar 2025 C2 M1 U3 Apache-2.0 Yes Details →
1.0.0rc1 13 Mar 2025 C2 M1 U3 Apache-2.0 Yes Details →
0.14.2rc1 04 Mar 2025 C2 M1 U3 Apache-2.0 Yes Details →
0.14.2b2 14 Feb 2025 C2 M1 U3 Apache-2.0 Yes Details →
0.14.2b1 02 Feb 2025 C2 M1 U3 Apache-2.0 Yes Details →
0.14.1 03 Jan 2025 C2 M1 U3 Apache-2.0 Yes Details →
0.14.1rc1 03 Jan 2025 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.14.0 29 Dec 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.14.0rc1 29 Dec 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.13.0 09 Dec 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.13.0rc1 09 Dec 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.12.10rc1 07 Dec 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.12.10b3 07 Dec 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.12.10b2 05 Dec 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.12.10b1 04 Dec 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.12.9 13 Nov 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.12.9rc1 13 Nov 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.12.8 02 Nov 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.12.8rc1 02 Nov 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.12.8b1 28 Oct 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.12.7 20 Oct 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.12.7rc1 20 Oct 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.12.7b1 11 Oct 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.12.6 07 Oct 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.12.6rc1 07 Oct 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.12.5 26 Sep 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.12.5rc1 26 Sep 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.12.5b1 16 Sep 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.12.4 11 Sep 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.12.4rc0 11 Sep 2024 C2 H2 M1 U5 Apache-2.0 Yes Details →
0.12.3 29 Aug 2024 C2 H2 M1 U5 Apache-2.0 Yes Details →
0.12.3rc0 29 Aug 2024 C2 H2 M1 U5 Apache-2.0 Yes Details →
0.12.2 23 Aug 2024 C2 H2 M1 U5 Apache-2.0 Yes Details →
0.12.1 23 Aug 2024 C2 H2 M1 U5 Apache-2.0 Yes Details →
0.12.1rc0 23 Aug 2024 C2 H2 M1 U5 Apache-2.0 Yes Details →
0.12.0 13 Aug 2024 C2 H2 M1 U5 Apache-2.0 Yes Details →
0.12.0rc0 13 Aug 2024 C2 H2 M1 U5 Apache-2.0 Yes Details →
0.11.1 07 Aug 2024 C2 H2 M1 U5 Apache-2.0 Yes Details →
0.11.0 05 Aug 2024 C2 H2 M1 U5 Apache-2.0 Yes Details →
0.11.0rc0 05 Aug 2024 C2 H2 M1 U5 Apache-2.0 Yes Details →
0.10.0 30 Jul 2024 C2 H2 M1 U5 Apache-2.0 Yes Details →
0.10.0rc2 30 Jul 2024 C2 H2 M1 U5 Apache-2.0 Yes Details →
0.10.0rc1 30 Jul 2024 C2 H2 M1 U5 Apache-2.0 Yes Details →
0.10.0rc0 29 Jul 2024 C2 H2 M1 U5 Apache-2.0 Yes Details →
0.9.5 22 Jul 2024 C2 H2 M1 U5 Apache-2.0 Yes Details →
0.9.5rc0 22 Jul 2024 C2 H2 M1 U5 Apache-2.0 Yes Details →
0.9.4 12 Jul 2024 C2 H2 M1 U5 Apache-2.0 Yes Details →
0.9.4rc0 12 Jul 2024 C2 H2 M1 U5 Apache-2.0 Yes Details →
0.9.3 29 Jun 2024 C2 H2 M1 U5 Apache-2.0 Yes Details →
0.9.3rc0 29 Jun 2024 C2 H2 M1 U5 Apache-2.0 Yes Details →
0.9.2 25 Jun 2024 C2 H2 M1 U5 Apache-2.0 Yes Details →
0.9.2rc1 25 Jun 2024 C2 H2 M1 U5 Apache-2.0 Yes Details →
0.9.1 19 Jun 2024 C2 H2 M1 U5 Apache-2.0 Yes Details →
0.9.1rc1 19 Jun 2024 C2 H2 M1 U5 Apache-2.0 Yes Details →
0.9.0 18 Jun 2024 C2 H2 M1 U5 Apache-2.0 Yes Details →
0.9.0rc1 18 Jun 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.8.0 10 Jun 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.8.0rc0 10 Jun 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.7.2 01 Jun 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.7.1 30 May 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.7.0 29 May 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.6.0 18 May 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.5.6 15 May 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.5.5 11 May 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.5.4 10 May 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.5.3 10 May 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.5.2 10 May 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.5.1 03 May 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.5.0 29 Apr 2024 C2 H1 M1 U4 Apache-2.0 Yes Details →
0.4.2 24 Apr 2024 C2 H1 M1 U4 — Yes Details →
0.4.1 04 Apr 2024 C2 H1 M1 U4 — Yes Details →
0.4.0 23 Feb 2024 C2 H1 M1 U4 — Yes Details →
0.3.4 20 Feb 2024 C2 H1 M1 U4 — Yes Details →
0.3.3 17 Feb 2024 C2 H1 M1 U4 — Yes Details →
0.3.2 17 Feb 2024 C2 H1 M1 U4 — Yes Details →
0.3.1 17 Feb 2024 C2 H1 M1 U4 — Yes Details →
0.0.1 13 Dec 2023 C2 H1 M1 U4 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1
  • 2025 1
  • 2026 10

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

03 Vulnerabilities

Recorded vulnerabilities for mesop

The 5 most severe of 12 vulnerabilities recorded for this package

Search all 12 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-33054: Mesop Path Traversal Vulnerability Leading to Denial of Service and File Manipulation 10.0 critical 1.2.3 29 Jun 2026
CVE-2026-33054: Mesop Path Traversal Vulnerability Leading to Denial of Service and File Manipulation 10.0 critical 1.2.3 18 Mar 2026
CVE-2026-33057: Mesop Unauthenticated Remote Code Execution via Test Suite Route /exec-py 9.8 critical 1.2.3 18 Mar 2026
CVE-2026-33057: Mesop Unauthenticated Remote Code Execution via Test Suite Route /exec-py 9.8 critical 1.2.3 29 Jun 2026
CVE-2025-30358: Mesop Class Pollution Vulnerability Leading to DoS and Jailbreak Attacks 8.1 high 0.14.1 27 Mar 2025

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 mesop

Is mesop safe to use?

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

Vulert scores mesop 58/100, which reads as usable, but worth attention. 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 mesop affected?

No. 1.3.7, 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 mesop should I use?

1.3.7 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 mesop have?

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

10 vulnerabilities were recorded for mesop in the last 12 months, and the oldest entry in this database dates to 18 Sep 2024. 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 mesop 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 mesop for upcoming vulnerabilities?

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