7.5

CVE-2026-2415: Unsafe variable evaluation in email templates

Analyzed
AliasesGHSA-r8p8-qw9w-j9qvPYSEC-2026-110
Published 16-02-2026Last modified 17-02-2026

Vulnerability summary

CVE-2026-2415 is a high (CVSS 7.5) Dynamic Variable Evaluation vulnerability in pretix. EPSS estimates a 0.29% chance of exploitation in the next 30 days, higher than 21.8% of scored vulnerabilities.

Priority
Routine

Not severe (CVSS 7.5, network access); no exploitation reported by the 5 checked sources

Source freshness unavailable

How is this decided?
CVSS score
7.5/10
010
High · v4.0 (CVE.org)
EPSS score
0.29%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Timeline

  1. 16-02-2026
    PublishedVulnerability first disclosed.
  2. 17-02-2026
    Last modifiedVulnerability information updated.

Description

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.

CVSS metrics

4 scores · 3 sources · 2 versions

EPSS trend

Probability

0.29%

Chance of exploitation in the next 30 days

Percentile

22%

Versus all other CVEs

30-day change

No change 0.00 pp

From 0.29% on 22-10-2026

22-10-202621-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Version check

Known conditions: network-reachable, low-privilege account, no user interaction (CVSS vector). Other conditions: not stated in public data.

Pretix1 product
  • pretix≥ 4.16.0, < 2025.9.0 | ≥ 2025.9.0, < 2025.10.0 | ≥ 2025.10.0, < 2026.1.0 | ≥ 2026.1.0, < 2026.1.1 | ≥ 4.16.0, < 2026.1.1
PyPI1 product
  • pretix≥ 2026.1.0, < 2026.1.1 | ≥ 2025.10.0, < 2025.10.2 | < 2025.9.4 | ≥ 4.16.0, < 2026.1.1

2 vendors · 2 products

References

8 links