CVE-2026-7666: An issue was discovered in Django 6.0 before 6.0.6 and 5.2 before 5.2.15. `django.core.mail.backends.smtp.Emai

Routine

LOW 3.1UPGRADE

CVE-2026-7666 is a low-severity flaw (CVSS 3.1) affecting django. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 aff

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	3.1 (Low)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.1% (top 96%)
CISA exploited list	No
Weakness	CWE-319
Published	2026-06-03
Last modified	2026-07-21

Publisher (CNA): Django Software Foundation · Vendor: djangoproject

Last updated 2026-07-21 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-06-03 14:16 UTCPublished CVE record published
2026-07-21 19:10 UTCUpdated Record last modified

djangoproject django UPGRADE

Affected: >= 5.2 and < 5.2.15 · >= 6.0 and < 6.0.6

Fixed in: 5.2.15, 6.0.6

Safe to downgrade to: a release before 5.2

1. Check installed version

apt-cache policy django || rpm -q django || django --version

2. UPGRADE to 5.2.15 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade django

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade django

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 5.2 (Debian / Ubuntu)

apt-cache madison django sudo apt install django=<VERSION_BEFORE_5.2> sudo apt-mark hold django

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list django sudo dnf downgrade django-<VERSION_BEFORE_5.2> sudo dnf versionlock add django

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-7666?

django: upgrade to 5.2.15, 6.0.6. Exact commands for each OS are on this page.

Is CVE-2026-7666 being exploited?

CVE-2026-7666 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-7666 affect?

CVE-2026-7666 affects django. Severity is low (CVSS 3.1). 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_si

How urgent is CVE-2026-7666?

Priority 12/100. No elevated risk signals yet.

Software pages

Django vulnerabilities

Related CVEs

CVE-2026-33034 HIGH 7.5 UPGRADE An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. ASGI requests with a mi
CVE-2026-4277 CRITICAL 9.8 UPGRADE An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Add permissions on inli
CVE-2026-3902 HIGH 7.5 UPGRADE An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. `ASGIRequest` allows a
CVE-2026-33033 MEDIUM 6.5 UPGRADE An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. `MultiPartParser` allow
CVE-2026-4292 LOW 2.7 UPGRADE An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Admin changelist forms

References

← Back to latest CVEs