Django GeoDjango vulnerable to denial of service through deeply nested geometry collections
An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. 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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-15830US | — | — | ||
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 parsin… | ||||
references
External citations — patches, advisories, analysis.
- https://docs.djangoproject.com/en/dev/releases/securityWEB
- https://github.com/advisories/GHSA-q238-5cxm-5c9hADVISORY
- https://github.com/django/djangoPACKAGE
- https://github.com/django/django/commit/1eafa1a80f1363283f89208ba4499ed54e35f085WEB
- https://github.com/django/django/commit/4353dfb56f8ba3a6fccc4bdd7f2ef2fbee3aa638WEB
- https://github.com/django/django/commit/62ef9d40cf4ea75f16518436b44b8ab2515340dfWEB
- https://github.com/django/django/commit/6af5da31775417c610dbf9c3f1b5b8333d42daf6WEB
- https://github.com/django/django/commit/75d401a1491e04a907ed745c128836d51c982c0fWEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan