CVE-2026-2415

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, pretix recommend that you rotate all passwords and API keys contained in your pretix.cfg https://docs.pretix.eu/self-hosting/config/  file.

CVE-2026-2415 has a CVSS score of 5.9 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.1.1, 2025.10.2, 2025.9.4); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-2415? CVE-2026-2415 is a high-severity security vulnerability in pretix (pip), affecting versions >= 2026.1.0, < 2026.1.1. It is fixed in 2026.1.1, 2025.10.2, 2025.9.4.
2. How severe is CVE-2026-2415? CVE-2026-2415 has a CVSS score of 5.9 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of pretix are affected by CVE-2026-2415? pretix (pip) versions >= 2026.1.0, < 2026.1.1 is affected.
4. Is there a fix for CVE-2026-2415? Yes. CVE-2026-2415 is fixed in 2026.1.1, 2025.10.2, 2025.9.4. Upgrade to this version or later.
5. Is CVE-2026-2415 exploitable, and should I be worried? Whether CVE-2026-2415 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-2415 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-2415?
   • Upgrade pretix to 2026.1.1 or later
   • Upgrade pretix to 2025.10.2 or later
   • Upgrade pretix to 2025.9.4 or later