5.3
Medium
CVE-2026-15830 An issue was discovered in Django 6.0 before 6.0.9 and 5.2 before 5.2.18
Description
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.GEOSGeometry` is subject to a potential denial-of-service when parsing deeply nested `GEOMETRYCOLLECTION` objects supplied as well-known text (WKT), well-known binary (WKB), or hex-encoded WKB, which triggers unbounded recursion and a segmentation fault in the underlying GEOS library. Spatial field lookups and the `django.contrib.gis.forms.GeometryField` form field are also affected. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Andrew MacPherson and kimchunbok_ for reporting this issue.
Affected products and versions
References
- Django security archive docs.djangoproject.com
- Django releases announcements groups.google.com
- github.com github.com
- github.com github.com
- github.com github.com
- github.com github.com
- Django security releases issued: 6.0.8 and 5.2.17 www.djangoproject.com
- github.com github.com
- github.com github.com
- github.com github.com
- github.com github.com
Timeline
- Published
- Last modified
Other CVEs of Django
The 62 CVEs of Django →
CVE-2026-114582
An issue was discovered in Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19
5.3
Medium
CVE-2026-113733
An issue was discovered in Django 6.1 before 6.1.3 and 6.0 before 6.0.10
2.2
Low
CVE-2026-113593
An issue was discovered in Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19
3.1
Low
CVE-2026-111362
An issue was discovered in Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19
5.3
Medium