Security release 2026.9.3 of pretix and pretix-adyen plugin
We have become aware of security issues in pretix due to external reports.
We therefore just released versions 2026.9.3, 2026.8.4, and 2026.7.6 of pretix as well as version 1.5.5 of pretix-adyen that fix these problems. It is strongly recommended that you update your installation as soon as possible.
If you are a customer of our pretix Hosted service, the vulnerabilities are already fixed for you and you do not need to take action.
Unsafe usage of return values [HIGH]
CVE ID: CVE-2026-131167
pretix offloads certain processes to background tasks that are run by a different server to avoid HTTP workers being clogged with processes that take longer than a usual web request. The browser periodically polls the server to see if the task is already finished using a UUID-shaped task ID. Once the task is completed, pretix resumes to the next step of the operation based on the result of the task. The system does however not check if the result stems from the correct type of task. Therefore, an attacker can supply the UUID of a task of a different type and pretix will continue with the result from the wrong task. In most cases, this will just result in an error because the return types do not match up, but in some cases this can be abused to extract objects the attacker usually should not see. Specifically, a vector was discovered that allowed to abuse this for unauthorized access to other people's ticket purchases. The attacker can, however, not control which purchases they get access to.
We have found no indication that this vulnerability was abused on pretix Hosted, however we can not rule it out with full certainty since (for privacy reasons) we only store logs in sufficient detail to analyze this for a short time frame.
Severity rating: Since this potentially leaks order data, even if it is hard to exploit, we consider the severity to be high.
Affected versions: All currently supported versions (except the fixed versions listed below) are affected.
This issue has been reported to us by Aaron Sagman.
Stored XSS in pretix-adyen [MEDIUM]
CVE ID: CVE-2026-131163
A stored XSS in pretix-adyen has been discovered where an attacker could configure his own ticket shop in a way that API calls are not made to Adyen, but an attacker-controlled server. Results of these API calls would then be embedded in a part of the shop without proper escaping, leading to full XSS including potential session takeover.
We have analyzed change history logs and have reason to believe that this vulnerability was not abused on pretix.eu.
Severity rating: Since this occurs on a page excluded from our content security policy, we assess the severity as high.
Affected versions: All currently supported versions (except the fixed versions listed below) are affected.
The original issue has been reported to us by Digant Prajapati and the possible exploit chain has been found internally.
Incorrect device security profile [MEDIUM]
CVE ID: CVE-2026-131166
When configuring a device to use the security profile "pretixSCAN (kiosk mode, no order sync, no search)", the API search endpoint introduced in pretix 4.12 was not blocked correctly. This theoretically allows these devices to perform searches for orders even if that was not intended. If the device is in kiosk mode, the search button will still be hidden from users.
Severity rating: This violates a clear security-boundary, but real-world effects are expected to be quite limited, therefore we consider the severity to be medium.
Affected versions: All pretix versions since 4.12 are affected.
This issue has been reported to us by Aaron Sagman.
Insufficient validation of payment status for Stripe [LOW]
CVE ID: CVE-2026-131170
Our payment integration with Stripe did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one payment. However, the attack requires knowledge of a valid charge ID from the same event which we believe is usually not exposed to users.
To simplify attack surface, the fix removes support for incoming webhooks regarding payments created through Stripe's old "source" API. pretix stopped creating payments using this API in 2024.1 for most payment methods and in 2024.9 for all payment methods.
Severity rating: Since no data exposure is at risk, the attack requires hard-to-obtain knowledge and large-scale exploitation is likely to be noticed, we assess the severity as low.
Affected versions: All currently supported versions (except the fixed versions listed below) are affected.
This issue has been reported to us by bowolalix and Aaron Sagman.
Validation bypass allows buying sold-out products [LOW]
CVE ID: CVE-2026-131168
A legacy code path allowed users to craft requests to a ticket shop that bypass some validation steps for the selected products. In consequence, this could lead to an attacker purchasing products that are in fact sold out.
Severity rating: This is a significant issue in pretix, but the security impact is low and it's unlikely that abuse stays undetected, we therefore assess the severity as low.
Affected versions: All currently supported versions (except the fixed versions listed below) are affected.
This issue has been reported to us by Aaron Sagman.
Link to parent order or ticket exposed in certain conditions [LOW]
CVE ID: CVE-2026-131164
When a ticket holder opens the ticket page of a ticket that is an add-on (possible since 2026.9) the HTML content of the page contains the secret link to the parent product, creating a potential data leak. Under different specific conditions, when a ticket contains user-uploaded files in response to a question, the page can even contain the secret link to the entire order.
Severity rating: Since this leak only exists inside a tiny group of attendees that likely know each other and only occurs under very rare conditions, we assess the severity as low.
Affected versions: All currently supported versions (except the fixed versions listed below) are affected.
This issue has been reported to us by Aaron Sagman.
Permissions are copied when copying scheduled exports [LOW]
CVE ID: CVE-2026-131169
When a scheduled export is copied, the permissions of the original export's owner are used when running the export. This allows users to create exports with data they usually shouldn't be able to see, but only within events they already have permissions to.
Severity rating: Since exploiting this still requires a significant level of permissions to the right organizer, we consider the severity to be low.
Affected versions: All currently supported versions (except the fixed versions listed below) are affected.
This issue has been reported to us by bowolalix.
Incorrect check of permissions in scheduled exports [LOW]
CVE ID: CVE-2026-131165
The fix for CVE-2026-127174 published in 2026.9.2 is incomplete: When expanding an export from "some events" to "all events", it is checked that the acting user is part of a team with permission to all events, but this check is not correctly bound to the organizer and could also be passed through permissions on a different organizer.
Severity rating: Since exploiting this still requires a significant level of permissions to the right organizer, we consider the severity to be low like the original bug.
Affected versions: All currently supported versions (except the fixed versions listed below) are affected.
This issue has been reported to us by Aaron Sagman.
Fixed versions
We just released updates for the last three stable versions on PyPI that fix the problem. If you run a pretix installation older than 2026.7, please upgrade to a recent version now.
We have also published a fixed plugin version:
We strongly recommend that you always run the latest version of pretix, as every release contains useful and important bug fixes, even if they are not security related.
If you want to keep updated about bugfix and security releases, you should follow this blog closely. A RSS feed is available and we also announce every blogpost on Mastodon.
We take the security of our product very seriously and always go the extra mile to make sure you stay safe. As we are humans, security issues unfortunately still might occur from time to time. We do everything we can to find and fix them as timely as we can. If you notice any security problems or have any questions on this topic, please contact us in private at security@pretix.eu. We will always treat your message with the appropriate priority.