CVE-2026-101271: Pretix OAuth access token revocation failure

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

Pretix, a ticketing and event management platform, does not revoke OAuth access tokens when an authorized application is manually disabled. An attacker who compromises an access token can continue using it indefinitely even after the application is deactivated, potentially maintaining unauthorized access to user data and event information.

Technologies: Pretix. Vendors: Pretix.

Quick answers

Is CVE-2026-101271 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-101271 being exploited in the wild.
How severe is CVE-2026-101271?
Informational severity, published 29 September 2026.
Which products and versions are affected?
Pretix Pretix.
Is there a fix for CVE-2026-101271?
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-101271 attacked?
It is attacked over the network.
Am I affected by CVE-2026-101271?
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

OAuth access tokens remain valid for their full lifetime even after the OAuth client application they are bound to is disabled. This is a logic flaw in token lifecycle management where token revocation is not triggered by client deactivation. An attacker with a valid access token can bypass application-level access controls to continue API operations after the legitimate application has been removed.

Affected products

  • Pretix Pretix

Timeline

  • 2026-09-29: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.