Is CVE-2026-41426 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-41426 being exploited in the wild.

How severe is CVE-2026-41426?

Medium severity, with a CVSS score of 6.1, published 24 April 2026.

Which products and versions are affected?

pretalx (PyPI) < 2026.1.0, ECOSYSTEM:introduced=0,fixed=2026.1.0.

Is there a fix for CVE-2026-41426?

Yes. pretalx (PyPI): upgrade to 2026.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-41426 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-41426?

Check whether you run Pretalx or pretalx (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-41426: pretalx email injection in mail templates via unescaped placeholders

Q: Which products and versions are affected?

pretalx (PyPI) < 2026.1.0, ECOSYSTEM:introduced=0,fixed=2026.1.0.

Q: Is there a fix for CVE-2026-41426?

Yes. pretalx (PyPI): upgrade to 2026.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-41426 attacked?

It is attacked over the network, in a web application.

Q: Am I affected by CVE-2026-41426?

Check whether you run Pretalx or pretalx (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-41426 · Severity: medium · CVSS 6.1 · Published 2026-04-24

pretalx, a conference management tool, is vulnerable to a flaw that allows attackers to send deceptive emails from the official system address. By using specially crafted names or profile information, an attacker can trick the system into sending phishing emails that appear legitimate to recipients. This could be used to steal user credentials or spread misinformation while bypassing standard email security filters.

Technologies: pretalx (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-41426 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-41426 being exploited in the wild.
How severe is CVE-2026-41426?: Medium severity, with a CVSS score of 6.1, published 24 April 2026.
Which products and versions are affected?: pretalx (PyPI) < 2026.1.0, ECOSYSTEM:introduced=0,fixed=2026.1.0.
Is there a fix for CVE-2026-41426?: Yes. pretalx (PyPI): upgrade to 2026.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-41426 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-41426?: Check whether you run Pretalx or pretalx (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

pretalx (PyPI): upgrade to 2026.1.0 or later
```
pip install "pretalx>=2026.1.0"
```

Technical details

A vulnerability in pretalx mail templates arises from improper neutralization of user-controlled placeholders (CWE-79, CWE-116). An unauthenticated attacker can inject malformed HTML or Markdown syntax into fields like account display names, speaker biographies, or proposal titles. When these fields are interpolated into system-generated emails (such as password reset or notification emails), the injected content is rendered, allowing the attacker to control the email's body. Because these emails originate from the legitimate configured sender and pass SPF/DKIM/DMARC checks, they serve as a highly effective phishing vector. The issue is fixed in version 2026.1.0.

Affected products

pretalx pretalx < 2026.1.0

Identifiers

CVE-2026-41426
GHSA-jm8c-9f3j-4378
PYSEC-2026-109

Timeline

2026-04-17: patched: Fix released in version 2026.1.0
2026-04-18: advisory: GitHub Advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.