pretix
Affected
- introduced
2026.1.0, fixed2026.1.1(ecosystem)
Fixed versions
2026.1.1
Fix
- Fixed version
2026.1.1pip install --upgrade pretix==2026.1.1
Advisory
Also known as: CVE-2026-2415, PYSEC-2026-110
pretix unsafely evaluates variables in emails
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:
{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.{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.
High Basis: The source's own band: HIGH
2026.1.0, fixed 2026.1.1 (ecosystem)2026.1.1
2026.1.1pip install --upgrade pretix==2026.1.12025.10.0, fixed 2025.10.2 (ecosystem)2025.10.2
2025.10.2pip install --upgrade pretix==2025.10.20, fixed 2025.9.4 (ecosystem)2025.9.4
2025.9.4pip install --upgrade pretix==2025.9.4Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0