CVE-2026-131170: Our payment integration with Stripe did not properly validate payment status responses
Source GCVE Database
Not known to be exploited · CVSS 6.3 Medium · fixed in 2026.9.3 : update pretix when convenient.
Data as of 20 Nov 2026, 13:43 UTC
Thin evidence
One scorer or none| CNA (pretix) | CVSS 4.0 | 6.3 |
|---|
- Patch
- Available – fixed in 2026.9.3, 2026.8.4, 2026.7.6
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade pretix to 2026.9.3, 2026.8.4 or 2026.7.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| pretixpretix | Affected
| Fixed in
|
| pretixpretix | Affected
| Fixed in
|
| pretixpretix | Affected
| Fixed in
|
GitHubpretixpkg:github/pretixOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The vendor has addressed the issue by removing support for incoming webhooks related to payments created through Stripe's deprecated "source" API. pretix stopped creating payments using this API in version 2024.1 for most payment methods and fully in 2024.9 for all payment methods. Users should upgrade to versions 2024.9 or later to ensure the fix is applied. No additional immediate action is indicated.
Description
A vulnerability in a payment integration with Stripe allowed improper validation of payment status responses. An attacker with knowledge of a valid charge ID could reuse a successful payment status from one payment to claim multiple tickets for different payments. The issue mainly affects payments created through Stripe's deprecated "source" API, which pretix stopped using in 2024.1 for most methods and completely by 2024.9.