# CVE-2026-2415: pretix unsafely evaluates variables in emails

Source: https://junglewise.ai/threats/cve-2026-2415-pretix-unsafely-evaluates-variables-in-emails  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-02-16  
License: CC BY 4.0 with a link back

CVE-2026-2415 · Severity: low · CVSS 3.1 · Published 2026-02-16

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.

Technologies: [pretix (PyPI)](https://junglewise.ai/threats/technologies/pypi-pretix). Vendors: [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

**Is CVE-2026-2415 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-2415 being exploited in the wild.

**How severe is CVE-2026-2415?** Low severity, with a CVSS score of 3.1, published 16 February 2026.

**Which products and versions are affected?** pretix (PyPI) ECOSYSTEM:introduced=2026.1.0,fixed=2026.1.1, ECOSYSTEM:introduced=4.16.0,fixed=2026.1.1.

**Is there a fix for CVE-2026-2415?** Yes. pretix (PyPI): upgrade to 2026.1.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2026-2415?** Check whether you run pretix (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- pretix (PyPI): upgrade to 2026.1.1 or later

  ```sh
  pip install "pretix>=2026.1.1"
  ```


## Affected products

- pretix (PyPI) ECOSYSTEM:introduced=2026.1.0,fixed=2026.1.1, ECOSYSTEM:introduced=4.16.0,fixed=2026.1.1

## Identifiers

- CVE-2026-2415
- GHSA-r8p8-qw9w-j9qv
- PYSEC-2026-110

## Related threats

- [PYSEC-2026-1802 - pretix has Broken Access Control Allowing Cross-User File Access via UUID](https://junglewise.ai/threats/cve-2025-14882-pretix-has-broken-access-control-allowing-cross-user-file-access)
- [PYSEC-2026-1801 - pretix allows Pillow to parse EPS files](https://junglewise.ai/threats/cve-2023-44464-pretix-allows-pillow-to-parse-eps-files)
- [rami.io pretix authorization bypass in API export endpoint](https://junglewise.ai/threats/cve-2026-9712-rami-io-pretix-authorization-bypass-in-api-export-endpoint)
- [rami.io pretix data isolation breach in check-in API](https://junglewise.ai/threats/cve-2026-5600-rami-io-pretix-data-isolation-breach-in-check-in-api)
- [PYSEC-2026-1803 - pretix has Broken Access Control Allowing Cross-User File Access via UUID](https://junglewise.ai/threats/cve-2025-14881-pretix-has-broken-access-control-allowing-cross-user-file-access)