CVE-2026-5600: Medium severity pretix pretix vulnerability
A new API endpoint introduced in pretix 2025 that is supposed to return all check-in events of a specific event in fact returns all check-in events belonging to the respective organizer. This allows an API consumer to access information for all other events under the same organizer, even those they should not have access to.
These records contain information on the time and result of every ticket scan as well as the ID of the matched ticket. Example:
{ "id": 123, "successful": true, "errorreason": null, "errorexplanation": null, "position": 321, "datetime": "2020-08-23T09:00:00+02:00", "list": 456, "created": "2020-08-23T09:00:00+02:00", "autocheckedin": false, "gate": null, "device": 1, "deviceid": 1, "type": "entry" }
An unauthorized user usually has no way to match these IDs (position) back to individual people.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
pip/pretixto a version that resolves this vulnerability.Fixed in 2026.1.2 - Upgrade
Upgrade
pip/pretixto a version that resolves this vulnerability.Fixed in 2026.2.1 - Upgrade
Upgrade
pip/pretixto a version that resolves this vulnerability.Fixed in 2026.3.1
Event History
Frequently Asked Questions
What is the severity of CVE-2026-5600?
CVE-2026-5600 is considered a medium-severity vulnerability due to its potential for unauthorized access to sensitive event data.
How do I fix CVE-2026-5600?
To fix CVE-2026-5600, update to pretix version 2026.2.1 or later.
What type of information can be accessed due to CVE-2026-5600?
CVE-2026-5600 allows an API consumer to access all check-in events belonging to the same organizer, potentially exposing confidential event details.
Which versions of pretix are affected by CVE-2026-5600?
Affected versions of pretix include any version between 2025.10.0 and 2026.1.2, as well as versions 2026.2.0 and below.
Is there a workaround for CVE-2026-5600?
Currently, there is no officially recommended workaround for CVE-2026-5600; the best practice is to update to a patched version.