pretix offloads certain processes to background tasks that are run by a different server to avoid HTTP workers being
Source GCVE Database
Not known to be exploited · CVSS 8.9 High · fixed in 2026.9.3 : patch pretix soon.
Data as of 20 Nov 2026, 13:41 UTC
Thin evidence
One scorer or none| CNA (pretix) | CVSS 4.0 | 8.9 |
|---|
- 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:H/VI:N/VA:N/SC:H/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
Since pretix is not a cloud service, remediation depends on vendor advisories or updates. Users should monitor for official vendor advisories for patch availability. If you cannot patch yet, restricting access to the task UUIDs and monitoring for unusual access patterns may help reduce risk, but no specific mitigations are detailed in the input.
Description
pretix uses background tasks identified by UUIDs to handle long-running processes separately from HTTP workers. A vulnerability exists where the system does not verify that the result corresponds to the correct task type, allowing an attacker to supply a UUID from a different task type. This can lead to unauthorized access to other users' ticket purchase information, although the attacker cannot control which purchases are accessed. Most attempts result in errors due to type mismatches. The vulnerability has a high severity score of 8.9.