Skip to main content
Menu
CVEs

pretix payment check bypass in Stripe integration

CVE-2026-131170Published , updated

6.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 2026.7.6, 2026.8.4, 2026.9.3
Who is exposed
Not reported

Summary

pretix's Stripe payment integration did not properly validate payment status responses, so a remote attacker, without logging in or any user action, could reuse a successful status response from one payment for a different payment and obtain multiple valid tickets for one payment. The attack requires a valid charge ID from the same event, which is believed to be usually not exposed to users.

Written by a model

Original 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.

What to do

Upgrade to a fixed version: 2026.7.6, 2026.8.4, 2026.9.3.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-131170 (Insufficient validation of payment status for Stripe), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-131170 (entry last updated 2026-11-20):
Affected:
- PyPI package pretix: fixed in 2026.7.6; from 2026.8.0, fixed in 2026.8.4; from 2026.9.0, fixed in 2026.9.3
Fixed versions: 2026.7.6, 2026.8.4, 2026.9.3.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-131170 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131170 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (PyPI): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://pretix.eu/about/en/blog/20261120-release-2026-9-3-adyen/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-131170
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131170"}.

Affected versions

cve.now Index

33Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach10/20Affects PyPI packages
  • Severity6.3/10CVSS 6.3
  • No patch0/5No signal

What would change the score

  • Would score about 78 if added to CISA KEV
  • Would score about 73 if CISA's SSVC rates exploitation active
  • Would score about 38 if advisories confirm default setups are exposed

Impact

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Advisorypretix.eu · about/en/blog/20261120-release-2026-9-3-adyen
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-131170
RecordNVD · CVE-2026-131170

Questions about CVE-2026-131170

Is CVE-2026-131170 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-131170?

pretix (PyPI): before 2026.7.6; from 2026.8.0 before 2026.8.4; from 2026.9.0 before 2026.9.3.

Source: cve.now feed data

How do I fix CVE-2026-131170?

Upgrade to a fixed version: 2026.7.6, 2026.8.4, 2026.9.3.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.