PatchTheCVEdjango vulnerabilities and fixes
Recent CVEs affecting django, with upgrade or downgrade steps. 4 tracked.
django has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 4. Most recent: 2026-08-04. Highest priority: CVE-2026-15307 (score 47/100).
- CVE-2026-15307 HIGH 8.8 UPGRADE An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. GeoDjango spatial lookups optimistic
- CVE-2026-15830 MEDIUM 5.3 UPGRADE An issue was discovered in Django 6.0 before 6.0.9 and 5.2 before 5.2.18. GeoDjango's `django.contrib.gis.geos
- CVE-2026-15337 MEDIUM 5.3 UPGRADE An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. `django.utils.translation.check_for_
- CVE-2026-15920 MEDIUM 6.1 UPGRADE An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. `django.contrib.admin.utils.display_
FAQ
How do I fix django vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is django being exploited right now?
None of the tracked django CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which django CVE should I patch first?
CVE-2026-15307 currently ranks highest (47/100): An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. GeoDjango spatial lookups optimistic.