https://seclists.org/oss-sec/2026/q1/141: Django CVE-2025-13473, CVE-2025-14550, CVE-2026-1207, CVE-2026-1285, CVE-2026-1287, and CVE-2026-1312
Published Feb 3, 2026
·Updated
Affected Software
4 affected components
Django Django
Django Django>4.2
Django Django>5.2
Django Django>6.0
Frequently Asked Questions
1
What is the severity of CVE-2025-13473?
CVE-2025-13473 is classified as a medium severity vulnerability in Django, which may allow unauthorized access under certain conditions.
2
What is the impact of CVE-2025-14550?
CVE-2025-14550 can lead to security breaches by allowing attackers to exploit specific weaknesses in Django applications.
3
How do I fix CVE-2025-13473?
To mitigate CVE-2025-13473, upgrade to the latest version of Django where the vulnerability has been patched.
4
What are the affected versions for CVE-2026-1207?
CVE-2026-1207 affects multiple versions of Django prior to the latest security release.
5
Is there a workaround for CVE-2026-1285?
While the best practice is to upgrade Django, specific configuration changes may serve as temporary workarounds for CVE-2026-1285 until an update is applied.