# CVE-2026-101269: Pretix API session token reuse across uploaded files

Source: https://junglewise.ai/threats/cve-2026-101269-the-mechanism-binding-api-uploaded-files-to-the-uploader-s  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-29. Updated: 2026-09-29  
License: CC BY 4.0 with a link back

CVE-2026-101269 · Severity: info · Published 2026-09-29

A ticket management system's API has a flaw where the same session token is reused across all token-based API users when uploading files, rather than binding uploads to individual users. Although the risk is limited because uploaded files are temporary and referenced by random identifiers, the authentication protection mechanism is effectively bypassed, potentially allowing unauthorized file access within the brief window of file availability.

Technologies: [Pretix](https://junglewise.ai/threats/technologies/pretix-pretix). Vendors: [Pretix](https://junglewise.ai/threats/vendors/pretix).

## Quick answers

**Is CVE-2026-101269 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-101269 being exploited in the wild.

**How severe is CVE-2026-101269?** Informational severity, published 29 September 2026.

**Which products and versions are affected?** Pretix Pretix.

**Is there a fix for CVE-2026-101269?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-101269 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-101269?** Check whether you run Pretix. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The API file upload mechanism fails to correctly bind uploaded files to the authenticating user's identity, instead reusing the same session token for all token-based API callers. An attacker with knowledge of another user's API token could theoretically access files uploaded by that user via the API. Mitigation is inherent: uploaded files exist only for 24 hours and are referenced by random UUIDs, making exploitation difficult in practice.

## Affected products

- Pretix Pretix

## Timeline

- 2026-09-29: disclosed

## References

- [https://pypi.python.org/](https://pypi.python.org/)
- [https://pretix.eu/about/en/blog/20260929-release-2026-7-1/](https://pretix.eu/about/en/blog/20260929-release-2026-7-1/)

## Related threats

- [pretix missing permission check in ticket layout API](https://junglewise.ai/threats/cve-2026-125744-our-api-endpoint-for-changing-ticket-layouts-did-not-properly)
- [Pretix payment status validation bypass in Adyen integration](https://junglewise.ai/threats/cve-2026-101275-our-payment-integration-with-adyen-did-not-properly-validate)
- [pretix improper validation of OpenID Connect response_type in SSO](https://junglewise.ai/threats/cve-2026-101274-when-pretix-is-used-as-the-identity-provider-in-a-single-sign-on)
- [pretix gift card ID enumeration and account credit increase](https://junglewise.ai/threats/cve-2026-101273-some-of-our-api-endpoints-allowed-to-create-order-payments)
- [pretix session validation bypass in API-created shredder exports](https://junglewise.ai/threats/cve-2026-101272-the-mechanism-binding-files-generated-during-a-shredding-process)