# CVE-2026-2452: Unsafe variable evaluation in email templates

> Attackers with backend access can exfiltrate sensitive system configuration data, including passwords and API keys, via crafted email template placeholders.

- **Severity:** High 7.5 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Feb 2026
- **Updated:** 17 Feb 2026
- **Also known as:** GHSA-mv9g-vp7w-xq67

## What is CVE-2026-2452?

CVE-2026-2452 is a high-severity vulnerability in pretix-newsletter, published on 16 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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 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.

Weakness: CWE-627 (Dynamic Variable Evaluation)

## Which versions are affected by CVE-2026-2452?

It affects 2 products.


Products: Pretix Newsletters, Pretix Pretix.

## How do I fix CVE-2026-2452?

No fix has been published for CVE-2026-2452 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-2452 being exploited?

There is no known exploitation of CVE-2026-2452 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-2452 and fix it if it is affected.

What it is: CVE-2026-2452 is a high-severity vulnerability in pretix-newsletter, published on 16 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-2452 in the wild and no public exploit code.

Affected product: pretix-newsletter. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-2452/ (Markdown: https://insights.sbomify.com/CVE-2026-2452/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-2452
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2452
- OSV: https://osv.dev/vulnerability/CVE-2026-2452

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-2452/
Summaries are generated and may contain mistakes; the official description above is the record.