CVE-2026-131169: pretix · Permissions are copied when copying scheduled exports
Affects pretixSource CVE Database V5
Not known to be exploited · CVSS 2.1 Low · fixed in 2026.9.3 : update pretix when convenient.
Data as of 20 Nov 2026, 11:50 UTC
Thin evidence
One scorer or none| CNA (pretix) | CVSS 4.0 | 2.1 |
|---|
- Patch
- Available – fixed in 2026.9.3, 2026.8.4, 2026.7.6
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:UExploitation 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
Upgrading pretix to versions 2026.7.6, 2026.8.4, or 2026.9.3 or later will remediate this vulnerability. Users should apply these official fixes to prevent unauthorized data exposure via copied scheduled exports.
Description
CVE-2026-131169 is a low-severity vulnerability in pretix where copying a scheduled export causes the permissions of the original export's owner to be used when running the export. This allows users to create exports containing data they normally should not access, but only within events where they already have permissions. The issue affects multiple versions prior to fixed releases in 2026.7.6, 2026.8.4, and 2026.9.3.