Vulnerability Database · PyPI · Package report

pretix: vulnerability history, versions and safety

pretix is a package in the PyPI ecosystem. Vulert records 22 vulnerabilities for it across 100 releases, from Mar 2023 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
22 vulnerabilities recorded H4 M3 L4 U11
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
13 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 pretix 2026.8.0 i

Updated on 23 Oct 2026

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

Package health score 61/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 2026.8.0 — unaffected i
  • Vulnerabilities on record 22 over 3 years · 13 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 7.8 i
  • With no published fix 0 i
  • Depended on by 11 packages i
  • Stars 2,541 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence non-standard 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 pretix, 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
2026.8.0 30 Sep 2026 none non-standard — Details →
2026.7.2 29 Sep 2026 none non-standard — Details →
2026.6.3 29 Sep 2026 none non-standard — Details →
2026.5.6 29 Sep 2026 none non-standard — Details →
2026.6.2 29 Sep 2026 none non-standard — Details →
2026.5.5 29 Sep 2026 none non-standard — Details →
2026.7.1 29 Sep 2026 none non-standard — Details →
2026.7.0 30 Jul 2026 none non-standard — Details →
2026.6.1 28 Jul 2026 none non-standard — Details →
2026.4.6 28 Jul 2026 none non-standard — Details →
2026.5.4 28 Jul 2026 none non-standard — Details →
2026.6.0 01 Jul 2026 none non-standard — Details →
2026.4.5 01 Jul 2026 none non-standard — Details →
2026.5.3 01 Jul 2026 none non-standard — Details →
2026.3.5.post1 01 Jul 2026 L1 U1 non-standard Yes Details →
2026.4.4 25 Jun 2026 none non-standard — Details →
2026.3.4 25 Jun 2026 L1 U1 non-standard Yes Details →
2026.5.2 25 Jun 2026 none non-standard — Details →
2026.4.3 09 Jun 2026 none non-standard — Details →
2026.3.3 09 Jun 2026 L1 U1 non-standard Yes Details →
2026.5.1 09 Jun 2026 none non-standard — Details →
2026.5.0 27 May 2026 none non-standard — Details →
2026.2.2 27 May 2026 L1 U1 non-standard Yes Details →
2026.3.2 27 May 2026 L1 U1 non-standard Yes Details →
2026.4.2 27 May 2026 none non-standard — Details →
2026.4.1 04 May 2026 L1 U1 non-standard Yes Details →
2026.4.0 28 Apr 2026 L1 U1 non-standard Yes Details →
2026.1.2 08 Apr 2026 L1 U1 non-standard Yes Details →
2026.2.1 08 Apr 2026 L1 U1 non-standard Yes Details →
2026.3.1 08 Apr 2026 L1 U1 non-standard Yes Details →
2026.3.0 30 Mar 2026 M1 L1 U2 non-standard Yes Details →
2026.2.0 24 Feb 2026 L1 U2 non-standard Yes Details →
2025.9.4 16 Feb 2026 L1 U2 non-standard Yes Details →
2025.10.2 16 Feb 2026 L1 U3 non-standard Yes Details →
2026.1.1 16 Feb 2026 L1 U2 non-standard Yes Details →
2026.1.0 26 Jan 2026 H1 L1 U3 non-standard Yes Details →
2025.8.3 19 Dec 2025 L1 U2 non-standard Yes Details →
2025.9.3 19 Dec 2025 L1 U2 non-standard Yes Details →
2025.10.1 19 Dec 2025 L1 U3 non-standard Yes Details →
2025.10.0 27 Nov 2025 L3 U5 non-standard Yes Details →
2025.9.2 27 Nov 2025 L1 U4 non-standard Yes Details →
2025.8.2 27 Nov 2025 L1 U4 non-standard Yes Details →
2025.7.3 27 Nov 2025 L1 U4 non-standard Yes Details →
2025.9.1 27 Nov 2025 L1 U4 non-standard Yes Details →
2025.8.1 27 Nov 2025 L1 U4 — Yes Details →
2025.7.2 27 Nov 2025 L2 U4 — Yes Details →
2025.9.0 30 Oct 2025 L1 U4 — Yes Details →
2025.8.0 29 Sep 2025 L1 U4 — Yes Details →
2025.7.1 23 Aug 2025 L2 U5 — Yes Details →
2025.7.0 20 Aug 2025 L2 U5 — Yes Details →
2025.6.0 27 Jun 2025 L2 U5 — Yes Details →
2025.5.0 30 May 2025 L2 U5 — Yes Details →
2025.4.0 28 Apr 2025 L2 U5 — Yes Details →
2025.3.0 26 Mar 2025 L2 U5 — Yes Details →
2025.2.0 25 Feb 2025 L2 U5 — Yes Details →
2025.1.0 31 Jan 2025 L2 U5 — Yes Details →
2024.11.0 27 Nov 2024 L2 U5 — Yes Details →
2024.10.0 29 Oct 2024 L2 U5 — Yes Details →
2024.9.0 27 Sep 2024 L2 U5 — Yes Details →
2024.8.0 28 Aug 2024 L2 U5 — Yes Details →
2024.7.1 23 Aug 2024 L2 U5 — Yes Details →
2024.6.1 23 Aug 2024 H1 L2 U6 — Yes Details →
2024.5.1 23 Aug 2024 H1 L2 U6 — Yes Details →
2024.7.0 26 Jul 2024 H1 L2 U6 — Yes Details →
2024.6.0 24 Jun 2024 H1 L2 U6 — Yes Details →
2024.5.0 24 May 2024 H1 L2 U6 — Yes Details →
2024.4.0 26 Apr 2024 H1 L2 U6 — Yes Details →
2024.3.0 27 Mar 2024 H1 L2 U6 — Yes Details →
2024.2.0 28 Feb 2024 H1 L2 U6 — Yes Details →
2023.10.2 21 Feb 2024 H1 M1 L2 U7 — Yes Details →
2023.8.1 21 Feb 2024 H1 M1 L2 U7 — Yes Details →
2023.9.1 21 Feb 2024 H1 M1 L2 U7 — Yes Details →
2024.1.1 21 Feb 2024 H1 L2 U6 — Yes Details →
2024.1.0 29 Jan 2024 H1 M1 L2 U7 — Yes Details →
2023.10.1.post1 17 Jan 2024 H1 M1 L2 U7 — Yes Details →
2023.10.0 29 Nov 2023 H1 M1 L2 U7 — Yes Details →
2023.9.0 27 Oct 2023 H1 M1 L2 U7 — Yes Details →
2023.8.0 26 Sep 2023 H1 M1 L2 U7 — Yes Details →
4.20.4 12 Sep 2023 H2 M2 L2 U9 — Yes Details →
2023.6.3 12 Sep 2023 H2 M2 L2 U9 — Yes Details →
2023.7.3 12 Sep 2023 H1 M1 L2 U7 — Yes Details →
4.20.2.post1 11 Sep 2023 H2 M2 L2 U9 — Yes Details →
2023.6.1 11 Sep 2023 H2 M2 L2 U9 — Yes Details →
2023.7.1 11 Sep 2023 H2 M1 L2 U8 — Yes Details →
2023.7.0 28 Jul 2023 H2 M2 L2 U9 — Yes Details →
2023.6.0 27 Jun 2023 H2 M2 L2 U9 — Yes Details →
4.20.1 12 Jun 2023 H2 M2 L2 U9 — Yes Details →
4.20.0 31 May 2023 H2 M2 L2 U9 — Yes Details →
4.19.0 26 Apr 2023 H2 M2 L2 U9 — Yes Details →
4.18.2.post1 30 Mar 2023 H2 M2 L2 U9 — Yes Details →
4.18.2 29 Mar 2023 H2 M2 L2 U9 — Yes Details →
4.18.1 29 Mar 2023 H2 M2 L2 U9 — Yes Details →
4.18.0 28 Mar 2023 H2 M2 L2 U9 — Yes Details →
4.15.1 06 Mar 2023 H2 M2 L2 U9 — Yes Details →
4.16.1 06 Mar 2023 H2 M2 L2 U10 — Yes Details →
4.17.1 06 Mar 2023 H2 M2 L2 U9 — Yes Details →
4.17.0 27 Feb 2023 H3 M2 L2 U10 — Yes Details →
4.16.0 30 Jan 2023 H2 M2 L2 U10 — Yes Details →
4.15.0 30 Nov 2022 H2 M2 L2 U9 — Yes Details →
4.14.0 28 Oct 2022 H2 M2 L2 U9 — Yes Details →
4.15.0.dev0 28 Oct 2022 H2 M2 L2 U9 — Yes Details →
4.13.1 04 Oct 2022 H2 M2 L2 U9 — Yes Details →
4.14.0.dev0 29 Sep 2022 H2 M2 L2 U9 — Yes Details →
4.13.0 29 Sep 2022 H2 M2 L2 U9 — Yes Details →
4.12.0 29 Jul 2022 H2 M2 L2 U9 — Yes Details →
4.9.1 05 Jul 2022 H2 M2 L2 U9 — Yes Details →
4.11.1 05 Jul 2022 H2 M2 L2 U9 — Yes Details →
4.10.1 05 Jul 2022 H2 M2 L2 U9 — Yes Details →
4.11.0 01 Jul 2022 H2 M2 L2 U9 — Yes Details →
4.10.0 27 May 2022 H2 M2 L2 U9 — Yes Details →
4.9.0 27 Apr 2022 H2 M2 L2 U9 — Yes Details →
4.8.0 31 Mar 2022 H2 M2 L2 U9 — Yes Details →
4.5.2 28 Feb 2022 H2 M2 L2 U9 — Yes Details →
4.6.1 28 Feb 2022 H2 M2 L2 U9 — Yes Details →
4.7.1 28 Feb 2022 H2 M2 L2 U9 — Yes Details →
4.7.0 25 Feb 2022 H2 M2 L2 U9 — Yes Details →
4.6.0 27 Jan 2022 H2 M2 L2 U9 — Yes Details →
4.3.1 26 Jan 2022 H2 M2 L2 U9 — Yes Details →
4.5.1 26 Jan 2022 H2 M2 L2 U9 — Yes Details →
4.4.1 26 Jan 2022 H2 M2 L2 U9 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 5
  • 2024 4
  • 2025 4
  • 2026 9

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

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 pretix

Is pretix safe to use?

Vulert records 22 vulnerabilities for pretix in PyPI: 0 critical, 4 high, 3 medium and 4 low, plus 11 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 pretix's Vulert package health score?

Vulert scores pretix 61/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 pretix affected?

No. 2026.8.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.

Which version of pretix should I use?

2026.8.0 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 pretix have?

22 vulnerabilities are recorded for pretix in the PyPI ecosystem: 0 critical, 4 high, 3 medium and 4 low, plus 11 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 pretix vulnerabilities disclosed?

13 vulnerabilities were recorded for pretix in the last 12 months, and the oldest entry in this database dates to 06 Mar 2023. 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 pretix 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 pretix for upcoming vulnerabilities?

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