Is CVE-2026-5600 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-5600 being exploited in the wild.

How severe is CVE-2026-5600?

Medium severity, with a CVSS score of 4.3, published 8 April 2026.

Which products and versions are affected?

pretix (PyPI) ECOSYSTEM:introduced=2025.10.0,fixed=2026.1.2,introduced=2026.2.0,fixed=2026.2.1,introduced=2026.3.0,fixed=2026.3.1, ECOSYSTEM:introduced=2026.3.0,fixed=2026.3.1.

Is there a fix for CVE-2026-5600?

Yes. pretix (PyPI): upgrade to 2026.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-5600 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-5600?

Check whether you run pretix (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-5600: rami.io pretix data isolation breach in check-in API

CVE-2026-5600 · Severity: medium · CVSS 4.3 · Published 2026-04-08

pretix is a popular open-source ticketing and event management platform. A security flaw in a recently introduced API endpoint allows users with access to one event to view ticket check-in data for all other events managed by the same organizer. While this data does not directly identify individuals, it exposes sensitive operational information such as ticket scan times and success rates across an organizer's entire portfolio.

Technologies: pretix (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-5600 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-5600 being exploited in the wild.
How severe is CVE-2026-5600?: Medium severity, with a CVSS score of 4.3, published 8 April 2026.
Which products and versions are affected?: pretix (PyPI) ECOSYSTEM:introduced=2025.10.0,fixed=2026.1.2,introduced=2026.2.0,fixed=2026.2.1,introduced=2026.3.0,fixed=2026.3.1, ECOSYSTEM:introduced=2026.3.0,fixed=2026.3.1.
Is there a fix for CVE-2026-5600?: Yes. pretix (PyPI): upgrade to 2026.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-5600 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-5600?: Check whether you run pretix (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

pretix (PyPI): upgrade to 2026.3.1 or later
```
pip install "pretix>=2026.3.1"
```

Technical details

An improper isolation vulnerability (CWE-653) exists in a new API endpoint introduced in pretix 2025. The endpoint, intended to return check-in events for a specific event, fails to properly scope results, instead returning all check-in records belonging to the respective organizer. An authenticated API consumer can exploit this to retrieve data including scan timestamps, device IDs, and internal ticket position IDs for events they should not have access to. The issue is resolved in versions 2026.1.2, 2026.2.1, and 2026.3.1.

Affected products

rami.io pretix 2025.10.0 to 2026.1.1, 2026.2.0, 2026.3.0

Identifiers

CVE-2026-5600
GHSA-wr8q-c73g-m7gp
PYSEC-2026-111

Timeline

2026-04-08: advisory: Vendor advisory and blog post published
2026-04-08: patched: Fixed versions 2026.1.2, 2026.2.1, and 2026.3.1 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.