Django up to 5.2.14/6.0.5 Email Content django.core.mail.backends.smtp.EmailBackend cleartext transmission

Summaryinfo

A vulnerability classified as problematic was found in Django up to 5.2.14/6.0.5. This issue affects the function django.core.mail.backends.smtp.EmailBackend of the component Email Content Handler. The manipulation results in cleartext transmission. This vulnerability is known as CVE-2026-7666. It is possible to launch the attack remotely. No exploit is available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Django up to 5.2.14/6.0.5. Affected is the function django.core.mail.backends.smtp.EmailBackend of the component Email Content Handler. The manipulation with an unknown input leads to a cleartext transmission vulnerability. CWE is classifying the issue as CWE-319. The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors. This is going to have an impact on confidentiality. CVE summarizes:

An issue was discovered in Django 6.0 before 6.0.6 and 5.2 before 5.2.15. `django.core.mail.backends.smtp.EmailBackend` in Django fails to prevent reuse of a partially-initialized connection after a failed `STARTTLS` handshake when `fail_silently=True`, which allows on-path network attackers to read email content via cleartext interception. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Kasper Dupont for reporting this issue.

The weakness was published by Kasper Dupont. The advisory is available at docs.djangoproject.com. This vulnerability is traded as CVE-2026-7666 since 05/01/2026. The exploitability is told to be difficult. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 06/04/2026). This vulnerability is assigned to T1040 by the MITRE ATT&CK project.

The vulnerability scanner Nessus provides a plugin with the ID 318410 (Linux Distros Unpatched Vulnerability : CVE-2026-7666), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 5.2.15 or 6.0.6 eliminates this vulnerability. The upgrade is hosted for download at docs.djangoproject.com.

The vulnerability is also documented in the vulnerability database at Tenable (318410). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

• Content Management System

Name

• Django

Version

• 5.2.0
• 5.2.1
• 5.2.2
• 5.2.3
• 5.2.4
• 5.2.5
• 5.2.6
• 5.2.7
• 5.2.8
• 5.2.9
• 5.2.10
• 5.2.11
• 5.2.12
• 5.2.13
• 5.2.14
• 6.0.0
• 6.0.1
• 6.0.2
• 6.0.3
• 6.0.4
• 6.0.5

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion