Technical impact
The flaw lies in the binding logic that associates files created during a shredding operation with the authentication token used to request them. Because the same session token is reused for all token‑based API users, the session validation mechanism cannot reliably distinguish between different users. This defect corresponds to CWE-384 (Session Fixation) and CWE-640 (Improper Verification of In-Application Credentials) and renders the intended protection mechanism ineffective. An attacker who obtains any valid API token could access any file generated by a shredder export, but the impact is mitigated by the short lifetime of the files and their random UUID names.
Affected Systems
The vulnerability affects Pretix installations that use the shredding export feature. Versions prior to the release that introduced the fix (2026.8.1) are impacted; the issue was noted as similar to a defect fixed in 2026.7.1 but missed in that correction. All releases before 2026.8.1 should be considered vulnerable, while 2026.8.1 and later include the corrected session‑token handling and additional hardening of related code.
Risk and Exploitability
With a CVSS score of 2.3 the severity is low, and the EPSS score is <1%. The vulnerability is not listed in the CISA KEV catalog. The attack vector is primarily API‑based; an attacker would need valid API credentials and could request a shredder export file, gaining access to the content of any file generated within the next 24 hours. Because the files are identified by random UUIDs and expire quickly, the practical risk is minimal, and no known exploit demonstrates more extensive compromise.