Vulnerability Database · PyPI · Package report

pymupdf: vulnerability history, versions and safety

pymupdf is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 2 releases, from Mar 2026 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
2 vulnerabilities recorded M1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 13 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on pymupdf 2.0.0 i

Updated on 23 Oct 2026

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

Package health score 82/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 2.0.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 6.9 i
  • With no published fix 0 i
  • Depended on by 2,299 packages i
  • Stars 10,910 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence non-standard 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 pymupdf, 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.0 19 Oct 2026 none non-standard — Details →
1.28.2 06 Aug 2026 none non-standard — Details →
1.28.0 29 Jun 2026 none non-standard — Details →
1.27.2.3 24 Apr 2026 none non-standard — Details →
1.27.2.2 20 Mar 2026 none non-standard — Details →
1.27.2 10 Mar 2026 none non-standard — Details →
1.27.1 11 Feb 2026 none non-standard — Details →
1.26.7 11 Dec 2025 none non-standard — Details →
1.26.6 05 Nov 2025 M1 U1 non-standard Yes Details →
1.26.5 10 Oct 2025 M1 U1 non-standard Yes Details →
1.26.4 25 Aug 2025 none non-standard — Details →
1.26.3 02 Jul 2025 none non-standard — Details →
1.26.1 11 Jun 2025 none non-standard — Details →
1.26.0 22 May 2025 none non-standard — Details →
1.25.5 31 Mar 2025 none non-standard — Details →
1.25.4 14 Mar 2025 none non-standard — Details →
1.25.3 06 Feb 2025 none non-standard — Details →
1.25.2 17 Jan 2025 none non-standard — Details →
1.25.1 11 Dec 2024 none non-standard — Details →
1.25.0 05 Dec 2024 none non-standard — Details →
1.24.14 19 Nov 2024 none non-standard — Details →
1.24.13 29 Oct 2024 none non-standard — Details →
1.24.12 21 Oct 2024 none non-standard — Details →
1.24.11 03 Oct 2024 none non-standard — Details →
1.24.10 02 Sep 2024 none non-standard — Details →
1.24.9 24 Jul 2024 none non-standard — Details →
1.24.8 22 Jul 2024 none non-standard — Details →
1.24.7 26 Jun 2024 none non-standard — Details →
1.24.6 25 Jun 2024 none non-standard — Details →
1.24.5 30 May 2024 none non-standard — Details →
1.24.4 16 May 2024 none non-standard — Details →
1.24.3 09 May 2024 none non-standard — Details →
1.24.2 17 Apr 2024 none non-standard — Details →
1.24.1 02 Apr 2024 none non-standard — Details →
1.24.0 21 Mar 2024 none non-standard — Details →
1.23.26 29 Feb 2024 none non-standard — Details →
1.23.25 20 Feb 2024 none non-standard — Details →
1.23.24 19 Feb 2024 none non-standard — Details →
1.23.23 18 Feb 2024 none non-standard — Details →
1.23.22 13 Feb 2024 none non-standard — Details →
1.23.21 01 Feb 2024 none non-standard — Details →
1.23.20 29 Jan 2024 none non-standard — Details →
1.23.19 25 Jan 2024 none non-standard — Details →
1.23.18 23 Jan 2024 none non-standard — Details →
1.23.17 22 Jan 2024 none non-standard — Details →
1.23.16 18 Jan 2024 none non-standard — Details →
1.23.15 16 Jan 2024 none non-standard — Details →
1.23.14 15 Jan 2024 none non-standard — Details →
1.23.13 15 Jan 2024 none non-standard — Details →
1.23.12 12 Jan 2024 none non-standard — Details →
1.23.11 12 Jan 2024 none non-standard — Details →
1.23.10 12 Jan 2024 none non-standard — Details →
1.23.9 11 Jan 2024 none non-standard — Details →
1.23.9rc2 08 Jan 2024 none non-standard — Details →
1.23.9rc1 02 Jan 2024 none non-standard — Details →
1.23.8 19 Dec 2023 none non-standard — Details →
1.23.7 30 Nov 2023 none non-standard — Details →
1.23.6 06 Nov 2023 none non-standard — Details →
1.23.5 13 Oct 2023 none non-standard — Details →
1.23.4 27 Sep 2023 none non-standard — Details →
1.23.3 01 Sep 2023 none non-standard — Details →
1.23.2 28 Aug 2023 none non-standard — Details →
1.23.2rc1 27 Aug 2023 none non-standard — Details →
1.23.1 24 Aug 2023 none non-standard — Details →
1.23.0 23 Aug 2023 none non-standard — Details →
1.23.0rc2 21 Aug 2023 none non-standard — Details →
1.23.0rc1 10 Aug 2023 none non-standard — Details →
1.22.5 21 Jun 2023 none non-standard — Details →
1.22.3 11 May 2023 none non-standard — Details →
1.22.2 26 Apr 2023 none non-standard — Details →
1.22.1 18 Apr 2023 none non-standard — Details →
1.22.0 14 Apr 2023 none non-standard — Details →
1.21.1 13 Dec 2022 none non-standard — Details →
1.21.0 08 Nov 2022 none non-standard — Details →
1.20.2 13 Aug 2022 none non-standard — Details →
1.20.1 27 Jun 2022 none non-standard — Details →
1.20.0 17 Jun 2022 none non-standard — Details →
1.19.6 05 Mar 2022 none non-standard — Details →
1.19.5 03 Feb 2022 none non-standard — Details →
1.19.4 01 Jan 2022 none non-standard — Details →
1.19.3 12 Dec 2021 none non-standard — Details →
1.19.2 20 Nov 2021 none non-standard — Details →
1.19.1 24 Oct 2021 none non-standard — Details →
1.19.0 17 Oct 2021 none non-standard — Details →
1.18.19 16 Sep 2021 none non-standard — Details →
1.18.18 16 Sep 2021 none non-standard — Details →
1.18.17 28 Aug 2021 none non-standard — Details →
1.18.16 08 Aug 2021 none non-standard — Details →
1.18.15 10 Jul 2021 none non-standard — Details →
1.18.14 02 Jun 2021 none non-standard — Details →
1.18.13 05 May 2021 none non-standard — Details →
1.18.12 10 Apr 2021 none non-standard — Details →
1.18.11 10 Apr 2021 none non-standard — Details →
1.18.10 22 Mar 2021 none non-standard — Details →
1.18.9 26 Feb 2021 none non-standard — Details →
1.18.8 04 Feb 2021 none AGPL-3.0-or-later — Details →
1.18.7 02 Feb 2021 none AGPL-3.0-or-later — Details →
1.18.6 07 Jan 2021 none AGPL-3.0-or-later — Details →
1.18.5 17 Dec 2020 none AGPL-3.0-or-later — Details →
1.18.4 20 Nov 2020 none AGPL-3.0-or-later — Details →
1.18.3 09 Nov 2020 none — — Details →
1.18.2 27 Oct 2020 none — — Details →
1.18.1 18 Oct 2020 none — — Details →
1.18.0 08 Oct 2020 none — — Details →
1.17.7 14 Sep 2020 none — — Details →
1.17.6 26 Aug 2020 none — — Details →
1.17.5 06 Aug 2020 none — — Details →
1.17.4 23 Jul 2020 none — — Details →
1.17.3 07 Jul 2020 none — — Details →
1.17.2 24 Jun 2020 none — — Details →
1.17.1 18 Jun 2020 none — — Details →
1.17.0 19 May 2020 none — — Details →
1.16.18 23 Apr 2020 none — — Details →
1.16.17 09 Apr 2020 none — — Details →
1.16.16 29 Mar 2020 none — — Details →
1.16.15 27 Mar 2020 none — — Details →
1.16.14 25 Mar 2020 none — — Details →
1.16.13 15 Mar 2020 none — — Details →
1.16.12 12 Mar 2020 none — — Details →
1.16.11 23 Feb 2020 none — — Details →

The newest 120 of 140 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for pymupdf

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →

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 pymupdf

Is pymupdf safe to use?

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

Vulert scores pymupdf 82/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 pymupdf affected?

No. 2.0.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 pymupdf have?

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

2 vulnerabilities were recorded for pymupdf in the last 12 months, and the oldest entry in this database dates to 19 Mar 2026. 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 pymupdf 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 pymupdf for upcoming vulnerabilities?

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