{"answers":{"affected":"7 open source packages ship an affected version, including pretix. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-2415 in the wild and no public exploit code.","fix":"Upgrade pretix to a fixed version for your release line: 2025.9.4, 2025.10.2 or 2026.1.1.","what":"CVE-2026-2415 is a high-severity code injection vulnerability in pretix, published on 16 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-2415 and fix it if it is affected.\n\nWhat it is: CVE-2026-2415 is a high-severity code injection vulnerability in pretix, published on 16 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-2415 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- pretix (PyPI): affected all versions; fixed in 2025.9.4\n- pretix (PyPI): affected all versions; fixed in 2025.9.4\n- pretix (PyPI): affected from 2025.10.0; fixed in 2025.10.2\n- pretix (PyPI): affected from 2025.10.0; fixed in 2025.10.2\n- pretix (PyPI): affected from 2026.1.0; fixed in 2026.1.1\n- pretix (PyPI): affected from 2026.1.0; fixed in 2026.1.1\n- pretix (PyPI): affected from 4.16.0; fixed in 2026.1.1\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-2415/ (Markdown: https://insights.sbomify.com/CVE-2026-2415/index.md)","id":"CVE-2026-2415","markdown":"https://insights.sbomify.com/CVE-2026-2415/index.md","name":"CVE-2026-2415","record":{"aliases":["GHSA-r8p8-qw9w-j9qv","PYSEC-2026-110"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"pretix ticketing system","requires_auth":"low_privilege","summary":"Attackers can inject code into email templates to exfiltrate sensitive system configuration data, including database passwords and API keys.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"rami.io","cpe":[{"product":"pretix","vendor":"pretix"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-627","name":"Dynamic Variable Evaluation"}],"description":"Emails sent by pretix can utilize placeholders that will be filled with customer data. For example, when {name}\n is used in an email template, it will  be replaced with the buyer's \nname for the final email. This mechanism contained two security-relevant\n bugs:\n\n  *  \nIt was possible to exfiltrate information about the pretix system through specially crafted placeholder names such as {{event.__init__.__code__.co_filename}}.\n This way, an attacker with the ability to control email templates \n(usually every user of the pretix backend) could retrieve sensitive \ninformation from the system configuration, including even database \npasswords or API keys. pretix does include mechanisms to prevent the usage of such \nmalicious placeholders, however due to a mistake in the code, they were \nnot fully effective for the email subject.\n\n  *  \nPlaceholders in subjects and plain text bodies of emails were \nwrongfully evaluated twice. Therefore, if the first evaluation of a \nplaceholder again contains a placeholder, this second placeholder was \nrendered. This allows the rendering of placeholders controlled by the \nticket buyer, and therefore the exploitation of the first issue as a \nticket buyer. Luckily, the only buyer-controlled placeholder available \nin pretix by default (that is not validated in a way that prevents the \nissue) is {invoice_company}, which is very unusual (but not\n impossible) to be contained in an email subject template. In addition \nto broadening the attack surface of the first issue, this could \ntheoretically also leak information about an order to one of the \nattendees within that order. However, we also consider this scenario \nvery unlikely under typical conditions.\n\nOut 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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Unsafe variable evaluation in email templates","id":"CVE-2026-2415","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":7,"n_references":1,"next":{"headline":"Geo Mashup \u003c= 1.13.17 - Unauthenticated SQL Injection via 'sort' Parameter","id":"CVE-2026-2416"},"packages":[{"ecosystem":"PyPI","fixed":["2025.9.4"],"introduced":["0"],"last_affected":[],"package":"pretix","purl":null,"source":"GHSA-r8p8-qw9w-j9qv"},{"ecosystem":"PyPI","fixed":["2025.9.4"],"introduced":["0"],"last_affected":[],"package":"pretix","purl":"pkg:pypi/pretix","source":"GHSA-r8p8-qw9w-j9qv"},{"ecosystem":"PyPI","fixed":["2025.10.2"],"introduced":["2025.10.0"],"last_affected":[],"package":"pretix","purl":null,"source":"GHSA-r8p8-qw9w-j9qv"},{"ecosystem":"PyPI","fixed":["2025.10.2"],"introduced":["2025.10.0"],"last_affected":[],"package":"pretix","purl":"pkg:pypi/pretix","source":"GHSA-r8p8-qw9w-j9qv"},{"ecosystem":"PyPI","fixed":["2026.1.1"],"introduced":["2026.1.0"],"last_affected":[],"package":"pretix","purl":null,"source":"GHSA-r8p8-qw9w-j9qv"},{"ecosystem":"PyPI","fixed":["2026.1.1"],"introduced":["2026.1.0"],"last_affected":[],"package":"pretix","purl":"pkg:pypi/pretix","source":"GHSA-r8p8-qw9w-j9qv"},{"ecosystem":"PyPI","fixed":["2026.1.1"],"introduced":["4.16.0"],"last_affected":[],"package":"pretix","purl":"pkg:pypi/pretix","source":"PYSEC-2026-110"}],"prev":{"headline":"Auth bypass in Server","id":"CVE-2026-2414"},"products":["pretix"],"published":"2026-02-16","related":[{"cvss_score":9.8,"headline":"pretix mishandles file validation","id":"CVE-2024-27447","kev_date_added":null,"published":"2024-02-26"},{"cvss_score":7.2,"headline":"Stored XSS in Placeholder Samples in Mail Preview","id":"CVE-2024-8113","kev_date_added":null,"published":"2024-08-23"},{"cvss_score":5.5,"headline":"pretix: API leaks check-in data between events of the same organizer","id":"CVE-2026-5600","kev_date_added":null,"published":"2026-04-08"},{"cvss_score":2.4,"headline":"Limited HTML injection in emails","id":"CVE-2025-13742","kev_date_added":null,"published":"2025-11-27"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-17","vendors":["pretix"]},"summary":"Attackers can inject code into email templates to exfiltrate sensitive system configuration data, including database passwords and API keys.","url":"https://insights.sbomify.com/CVE-2026-2415/"}