Incorrect session validation for API-created shredder exports
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2026.6.4, 2026.7.3, 2026.8.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
This vulnerability affects the software's shredding feature when it creates export files through the API. Because all token-based API users share the same session token, the safeguard that should tie those temporary files to their authentication method does not work, though the practical risk is low because the files have random identifiers and exist for only a day.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
The mechanism binding files generated during a shredding process to the authentication method is not working correctly and the same session token is used for all token-based API users. This is similar to an issue fixed in 2026.7.1 but was missed while creating the fix. Since the files are referred to by randomly generated UUIDs and only exist for a day, there is virtually no risk, but it renders the added protection mechanism useless. As part of the fix, we have also improved hardening of some other related code areas.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- pretix
fixed in 2026.6.4; From 2026.7.0 · fixed in 2026.7.3; From 2026.8.0 · fixed in 2026.8.1