Vulnerability in pretix (CVE-2026-5600)
Summary
Vulnerability in pretix (CVE-2026-5600). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2026.1.2, 2026.2.1, 2026.3.1 or later.
Original description
The description as published by the source.
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: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.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-5600 has been found in pretix.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade pretix to 2026.1.2, 2026.2.1, 2026.3.1 or later.
If unsure, ask your IT team or search "pretix CVE-2026-5600" on the vendor's site.
CVE-2026-5600 (pretix) — CWE-653 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 2026.1.2, 2026.2.1, 2026.3.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-653) exists in pretix.
Check the vendor advisory for the affected versions of pretix.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 2026.1.2, 2026.2.1, 2026.3.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'pretix' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'pretix' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
pretixを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade pretix to 2026.1.2, 2026.2.1, 2026.3.1ステージング環境で 2026.1.2, 2026.2.1, 2026.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- advisory github.com
- package github.com
- web pretix.eu
- web pretix.eu
- web github.com
- web pypi.python.org