Unsafe variable evaluation in email templates
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 a security-relevant bug: 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 this plugin. 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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-2452
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 19:36 UTC · Revision 1
Source evidence
Unsafe variable evaluation in email templates
core-osv · Original sourcePublished 16 Feb 2026, 10:16 UTC
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 a security-relevant bug: 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 this plugin. 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.
osv:CVE-2026-2452
Complete source record
{
"id": "d65518f0aa27a93134349a73ee755d5d1ec95377f4f2ecf7f4e3f91198114c7f",
"url": "https://osv.dev/vulnerability/CVE-2026-2452",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Unsafe variable evaluation in email templates",
"summary": "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 a security-relevant bug: 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 this plugin. 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.",
"evidence": "osv:CVE-2026-2452",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2026-2452",
"aliases": [
"CVE-2026-2452"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "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"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/pretix/pretix",
"type": "GIT",
"events": [
{
"introduced": "065e6d402402bbc847dd3cb01b0700f88352886e"
},
{
"fixed": "0818ea6b45b5df2f657b57d2195b700c2f67a158"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:pretix:pretix:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "4.16.0"
},
{
"fixed": "2026.1.1"
}
],
"source": "CPE_RANGE"
}
]
}
}
],
"versions": [
"v2026.1.0",
"v2025.10.0",
"v2025.9.0",
"v2025.8.0",
"v2025.7.0",
"v2025.6.0",
"v2025.5.0",
"v2025.4.0",
"v2025.3.0",
"v2025.2.0",
"v2025.1.0",
"v2024.11.0",
"v2024.10.0",
"v2024.9.0",
"v2024.8.0",
"v2024.7.0",
"v2024.6.0",
"v2024.5.0",
"v2024.4.0",
"v2024.3.0",
"v2024.2.0",
"v2023.8.0",
"v2023.9.0",
"v2024.1.0",
"v2023.10.0",
"v2023.7.0",
"v2023.6.0",
"v4.20.0",
"v4.19.0",
"v4.18.0",
"v4.16.0",
"v4.17.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-2452.json"
}
}
],
"modified": "2026-10-28T02:30:22.770474928Z",
"provider": "osv",
"references": [
"https://marketplace.pretix.eu/",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/2xxx/CVE-2026-2452.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-2452",
"https://pretix.eu/about/en/blog/20260216-release-2026-1-1/"
],
"provider_metadata": {
"cwe_ids": [
"CWE-627"
],
"cna_assigner": "rami.io",
"unresolved_ranges": [
{
"extracted_events": [
{
"range": [
{
"introduced": "1.0.0"
},
{
"fixed": "1.6.3"
}
],
"source": "AFFECTED_FIELD",
"strategy": "ChangesAt"
}
]
},
{
"extracted_events": [
{
"range": [
{
"introduced": "2.0.0"
},
{
"fixed": "2.0.1"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
}
]
}
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/2xxx/CVE-2026-2452.json"
}
},
"related_cves": [
{
"value": "CVE-2026-2452",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 489245,
"published_at": "2026-02-16T10:16:22.027+00:00"
}