CVE-2026-131170: medium-severity vulnerability in pretix
Insufficient validation of payment status for Stripe
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 6.3epss 0.3%
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.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
Affected products
pretix · pretixRelated CVEs — pretix
In the same product, most dangerous first.
CVE-2026-131167HIGHUnsafe usage of return valuesEPSS 0.7%CVE-2026-131168MEDIUMValidation bypass allows buying sold-out productsEPSS 0.6%CVE-2026-131165LOWIncorrect check of permissions in scheduled exportsEPSS 0.5%CVE-2026-131169LOWPermissions are copied when copying scheduled exportsEPSS 0.5%CVE-2026-131164LOWLink to parent order or ticket exposed in certain conditionsEPSS 0.5%CVE-2026-131166MEDIUMIncorrect device security profileEPSS 0.5%