CVE-2026-131170
Deferred Deferred - Pending Action

Authentication Bypass via Stripe Payment Status Spoofing in pretix

Vulnerability report for CVE-2026-131170, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-20

Last updated on: 2026-11-20

Assigner: rami.io

Description

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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-20
Last Modified
2026-11-20
Generated
2026-11-20
AI Q&A
2026-11-20
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
pretix pretix to 2024.1 (exc)
pretix pretix to 2024.9 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The vulnerability involves improper validation of payment status responses in a Stripe integration. An attacker could reuse a valid payment status from one transaction to gain access to multiple tickets without making additional payments. This requires knowledge of a valid charge ID, which is typically not exposed to users.

Detection Guidance

This vulnerability involves improper validation of Stripe payment status responses. Detection requires checking payment logs for duplicate ticket issuance from a single payment or mismatched charge IDs. Review pretix payment logs for unusual patterns where one payment grants multiple tickets.

Impact Analysis

If exploited, this vulnerability could allow an attacker to obtain multiple valid tickets using a single payment. This could lead to financial losses for the ticketing system and potential misuse of event access. However, the attack is limited by the need for a valid charge ID.

Mitigation Strategies

Apply the latest pretix update to remove support for Stripe's old 'source' API webhooks. Verify no active webhooks remain for this deprecated API. Monitor payment logs for suspicious activity where a single payment generates multiple valid tickets.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-131170. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...