How severe is CVE-2026-5600?

No CVSS score has been assigned to CVE-2026-5600 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-5600?

CVE-2026-5600 affects the following packages: pretix (PyPI), pretix (PyPI), pretix (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2026-5600?

Update pretix to 2026.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-5600 is resolved across your whole dependency graph.

How do I detect CVE-2026-5600 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pretix, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-5600 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2026-5600 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-5600 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-5600?

CVE-2026-5600 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 17th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-5600?

CVE-2026-5600 is classified as CWE-653 (CWE-653). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-5600 published, and has it been updated?

CVE-2026-5600 was published on April 8, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2026-5600 — pretix

CVE-2026-5600 is a CWE-653 vulnerability in pretix. A fix is available for pretix — see the affected versions and patch details below.

pretix: API leaks check-in data between events of the same organizer

Also known asGHSA-wr8q-c73g-m7gpPYSEC-2026-111

Published

Apr 8, 2026

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-5600.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs17th percentile — riskier than 17% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

🐍pretix🐍pretix🐍pretix

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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, "error_reason": null, "error_explanation": null, "position": 321, "datetime": "2020-08-23T09:00:00+02:00", "list": 456, "created": "2020-08-23T09:00:00+02:00", "auto_checked_in": false, "gate": null, "device": 1, "device_id": 1, "type": "entry" }

An unauthorized user usually has no way to match these IDs (position) back to individual people.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`pretix`	≥ 2026.3.0&&< 2026.3.1	2026.3.1`pip install --upgrade 'pretix==2026.3.1'`
🐍PyPI	`pretix`	≥ 2026.2.0&&< 2026.2.1	2026.2.1`pip install --upgrade 'pretix==2026.2.1'`
🐍PyPI	`pretix`	≥ 2025.10.0&&< 2026.1.2	2026.1.2`pip install --upgrade 'pretix==2026.1.2'`

Affected Products

1 product · 3 configurations

Application

pretixpretix

≥ 2026.3.0 && < 2026.3.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pretix, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pretix to 2026.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-5600 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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, "error_reason": null, "error_explanation": null, "position": 321, "datetime": "2020-08-23T09

O3 Security · Impact-Aware SCA

Is CVE-2026-5600 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works