Vulnerability in django (CVE-2026-7666)
Summary
Vulnerability in django (CVE-2026-7666). Risk of unauthorized operations or information disclosure. Exploitable via STARTTLS. Mitigation: upgrade to 5.2.15, 6.0.6 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-7666 has been found in django.
Attackers can target a specific entry point like STARTTLS over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.1/10.
What to do: upgrade django to 5.2.15, 6.0.6 or later.
If unsure, ask your IT team or search "django CVE-2026-7666" on the vendor's site.
CVE-2026-7666 (django) — CWE-319 / CVSS v3 3.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: STARTTLS
Patched: 5.2.15, 6.0.6 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-319) exists in django. Attackers reach the vulnerable code path via STARTTLS without authentication.
Check the vendor advisory for the affected versions of django. Attack surface: STARTTLS.
Severity: Low (CVSS 3.1/10). Risk of unauthorized operations or information disclosure.
Update to 5.2.15, 6.0.6.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'django' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'django' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
djangoを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade django to 5.2.15, 6.0.6ステージング環境で 5.2.15, 6.0.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-7666 python-django
- Ubuntu UBUNTU-CVE-2026-7666 python-django
References
- advisory groups.google.com
- advisory github.com
- patch docs.djangoproject.com
- patch djangoproject.com
- web nvd.nist.gov
- web docs.djangoproject.com
- web djangoproject.com
- web github.com