django
Affected
- introduced
0, fixed5.2.17, introduced6.0, fixed6.0.8(ecosystem)
Fixed versions
5.2.17, 6.0.8
Fix
- Fixed version
5.2.17pip install --upgrade django==5.2.17 - Fixed version
6.0.8pip install --upgrade django==6.0.8
Advisory
Also known as: BIT-django-2026-15830, CVE-2026-15830, GHSA-q238-5cxm-5c9h
The record has no summary.
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.
Not rated by the source.
0, fixed 5.2.17, introduced 6.0, fixed 6.0.8 (ecosystem)5.2.17, 6.0.8
5.2.17pip install --upgrade django==5.2.176.0.8pip install --upgrade django==6.0.8Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: PyPA Advisory Database · CC BY 4.0