cve.bz

CVE-2026-2415 pretix pretix: Dynamic Variable Evaluation

7.5 highEPSS 0.3%Fix available

High (7.5) in pretix pretix. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in pretix 2025.10.2, 2025.9.4, 2026.1.1.

On this page
Emails sent by pretix can utilize placeholders that will be filled with customer data. For example, when {name} is used in an email template, it will be replaced with the buyer's name for the final email. This mechanism contained two security-relevant bugs: * It was possible to exfiltrate information about the pretix system through specially crafted placeholder names such as {{event.__init__.__code__.co_filename}}. This way, an attacker with the ability to control email templates (usually every user of the pretix backend) could retrieve sensitive information from the system configuration, including even database passwords or API keys. pretix does include mechanisms to prevent the usage of such malicious placeholders, however due to a mistake in the code, they were not fully effective for the email subject. * Placeholders in subjects and plain text bodies of emails were wrongfully evaluated twice. Therefore, if the first evaluation of a placeholder again contains a placeholder, this second placeholder was rendered. This allows the rendering of placeholders controlled by the ticket buyer, and therefore the exploitation of the first issue as a ticket buyer. Luckily, the only buyer-controlled placeholder available in pretix by default (that is not validated in a way that prevents the issue) is {invoice_company}, which is very unusual (but not impossible) to be contained in an email subject template. In addition to broadening the attack surface of the first issue, this could theoretically also leak information about an order to one of the attendees within that order. However, we also consider this scenario very unlikely under typical conditions. Out of caution, we recommend that you rotate all passwords and API keys contained in your pretix.cfg https://docs.pretix.eu/self-hosting/config/  file.

Severity

CVSS 4.0

7.5 high
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P/RE:L/U:Red

CVSS 3.1

5.9 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 22nd 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: total, assessed 2026-02-17. 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-627 Dynamic Variable Evaluation
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-2415 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-2415?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-2415?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-2415 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 4.16.0 before 2025.9.0
pretixfrom 2025.9.0 before 2025.10.0
pretixfrom 2025.10.0 before 2026.1.0
pretixfrom 2026.1.0 before 2026.1.1

Fixed in

ProductFixed in
pretix2025.9.4
pretix2025.10.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-r8p8-qw9w-j9qvPyPIpretix>=2026.1.0 <2026.1.12026.1.1
GHSA-r8p8-qw9w-j9qvPyPIpretix>=2025.10.0 <2025.10.22025.10.2
GHSA-r8p8-qw9w-j9qvPyPIpretix<2025.9.42025.9.4
PYSEC-2026-110PyPIpretix>=4.16.0 <2026.1.12026.1.1

References

Check your stackJSON