cve.bz

CVE-2026-9712 pretix pretix

3.8 lowEPSS 0.2%Fix available

Low (3.8) in pretix pretix. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in pretix 2026.4.2.

On this page
When creating an export through the pretix API, API clients are returned an UUID value for their export job (a long, random string like 35742818-c375-4d15-839f-d49aecce94d6). Using this UUID, the API client can then request the actual file for download. The same kind of UUID is used in other places in pretix when temporary files are generated for internal use or download. One remaining API endpoint, however, wrongfully did not verify if the UUID used for download actually belongs to a file that is supposed to be downloadable and belongs to the correct user. In reality, this is hard to exploit because an attacker would need to have access to a valid UUID for the file they desire which is unlikely to happen without a separate security problem giving them access to logs etc.

Severity

CVSS 4.0

3.8 low
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:U
EPSS
0.2% (unchanged from 0.2% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 12th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-05-28. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-639 Authorization Bypass Through User-Controlled Key
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • pretix (PyPI): fixed in 2026.4.2
  • pretix pretix: fixed in 2026.2.2
  • pretix pretix: fixed in 2026.3.2
  • pretix pretix: fixed in 2026.4.2

Ask an AI about this CVE

Show the promptExplain CVE-2026-9712 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-9712?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-9712?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-9712 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
pretixfrom 2024.10.0 before 2026.2.0
pretixfrom 2026.2.0 before 2026.3.0
pretixfrom 2026.3.0 before 2026.4.0
pretixfrom 2026.4.0 before 2026.5.0

Fixed in

ProductFixed in
pretix2026.2.2
pretix2026.3.2
pretix2026.4.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-72p9-6vv6-gvqhPyPIpretix<2026.4.22026.4.2
PYSEC-2026-2960PyPIpretix<2026.4.22026.4.2

References

Check your stackJSON