CVE-2026-131170: Insufficient validation of payment status for Stripe
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.
Affected Software
Event History
Frequently Asked Questions
What does an attacker need to exploit this issue?
The attacker needs a valid Stripe charge ID from another payment for the same event, along with a successful payment-status response that can be supplied for a different payment. The available information indicates that charge IDs are usually not exposed to users.
What is the practical impact of successful exploitation?
An attacker could obtain multiple valid tickets while making only one payment by reusing a successful payment status response across different payments.
Are installations still creating the affected type of Stripe payment?
pretix stopped creating Stripe payments through the old "source" API for most payment methods in 2024.1 and for all payment methods in 2024.9. The fix removes support for incoming webhooks for payments created through that API.