pretix unauthorized access to ticket purchases via task results
Affects pretix releases before 2026.7.6, 2026.8.0 to 2026.8.3, and 2026.9.0 to 2026.9.2, in the flows that use background tasks. Fixed in 2026.7.6, 2026.8.4, and 2026.9.3.
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.7.6, 2026.8.4, 2026.9.3
- Who is exposed
- Not reported
Summary
pretix, the ticketing software, has a flaw in how it handles results from background tasks: it does not check that a finished task is the type it expects. Remotely, without logging in, an attacker can supply the ID of a task of another type and gain unauthorized access to other people's ticket purchases, though they cannot choose which purchases they see.
Written by a model
Original description
pretix offloads certain processes to background tasks that are run by a different server to avoid HTTP workers being clogged with processes that take longer than a usual web request. The browser periodically polls the server to see if the task is already finished using a UUID-shaped task ID. Once the task is completed, pretix resumes to the next step of the operation based on the result of the task. The system does however not check if the result stems from the correct type of task. Therefore, an attacker can supply the UUID of a task of a different type and pretix will continue with the result from the wrong task. In most cases, this will just result in an error because the return types do not match up, but in some cases this can be abused to extract objects the attacker usually should not see. Specifically, a vector was discovered that allowed to abuse this for unauthorized access to other people's ticket purchases. The attacker can, however, not control which purchases they get access to.
Who should check
Operators of self-hosted pretix installations on supported versions; pretix Hosted customers are already fixed according to the advisory.
“All currently supported versions (except the fixed versions listed below) are affected.”
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-131167 (Unsafe usage of return values), 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-131167 (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.
Conditions (all must be true for the bug to be hit):
- Running a pretix version that is currently supported and older than the fixed releases (source: https://pretix.eu/about/en/blog/20261120-release-2026-9-3-adyen/)
- The affected flow uses background tasks, which pretix runs for certain processes (source: https://pretix.eu/about/en/blog/20261120-release-2026-9-3-adyen/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-131167 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131167 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-131167
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-131167"}.Affected versions
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach10/20Affects PyPI packages
- Severity8.9/10CVSS 8.9
- No patch0/5No signal
What would change the score
- Would score about 81 if added to CISA KEV
- Would score about 76 if CISA's SSVC rates exploitation active
- Would score about 41 if advisories confirm default setups are exposed
Impact
- Widely usedpretix has 1.7k weekly downloads. pypistats.org11 packages depend on pretix. deps.dev
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | pretix.eu · about/en/blog/20261120-release-2026-9-3-adyen |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-131167 |
| Record | NVD · CVE-2026-131167 |
Questions about CVE-2026-131167
Is CVE-2026-131167 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
What does this mean?
pretix can continue with the result of a background task of a different type. This can expose objects that the requester should not see, including other people's ticket purchases.
Source: pretix.eu
Which versions are affected by CVE-2026-131167?
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
Am I affected, and how do I check?
All currently supported pretix versions are affected except the fixed releases, so the affected ranges are before 2026.7.6, 2026.8.0 to before 2026.8.4, and 2026.9.0 to before 2026.9.3. The issue concerns flows that use background tasks, which pretix runs for certain processes, so compare the installed pretix version against these ranges.
Source: pretix.eu
How do I fix CVE-2026-131167?
Upgrade to 2026.7.6, 2026.8.4, or 2026.9.3, matching your release line. These are the fixed versions listed for this vulnerability.
Source: pretix.eu
Related
- CVE-2024-27447pretix before 2024.1.1 mishandles file validation.
- CVE-2026-2415Unsafe variable evaluation in email templates
- CVE-2024-8113Stored XSS in Placeholder Samples in Mail Preview
- CVE-2026-101274When pretix is used as the identity provider in a Single-Sign-On (SSO) setup for customer accounts, the system did not properly validate…
- CVE-2026-131168Validation bypass allows buying sold-out products
- CVE-2026-131170Insufficient validation of payment status for Stripe
No corrections so far. Something wrong on this page? Report an error.