CVE-2024-56374Medium· 5.8▾ SunlitDjango has a potential denial-of-service vulnerability in IPv6 validation
▾ Sunlit zone — Low / medium · no exploitation signal
impact 31.9 · likelihood 0.4 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Sep 12.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
1.9%
An issue was discovered in Django 5.1 before 5.1.5, 5.0 before 5.0.11, and 4.2 before 4.2.18. Lack of upper-bound limit enforcement in strings passed when performing IPv6 validation could lead to a potential denial-of-service attack. The undocumented and private functions clean_ipv6_address and is_valid_ipv6_address are vulnerable, as is the django.forms.GenericIPAddressField form field. (The django.db.models.GenericIPAddressField model field is not affected.)
django >= 5.1, < 5.1.5django >= 5.0, < 5.0.11django >= 4.2, < 4.2.18django >= 5.1, < 5.1.5django >= 5.0, < 5.0.11django >= 4.2, < 4.2.18Upgrade to a patched release:
django 5.1.5django 5.0.11django 4.2.18django 5.1.5django 5.0.11django 4.2.18Connected by shared product, vendor, weakness, or advisory.
CVE-2026-5766Medium· 5.3Django has an Improper Handling of Length Parameter Inconsistency
CVE-2025-64460MediumDjango is vulnerable to DoS via XML serializer text extraction
CVE-2025-13372Medium· 4.3Django is vulnerable to SQL injection in column aliases
CVE-2025-64458High· 7.5Django has a denial-of-service vulnerability in HttpResponseRedirect and HttpResponsePermanentRedirect on Windows
CVE-2025-26699Medium· 5.0Django vulnerable to Allocation of Resources Without Limits or Throttling
CVE-2026-4292Low· 2.7Django vulnerable to privilege abuse in ModelAdmin.list_editable