Django Software Foundation up to 5.2.16/6.0.7 GEOS Geometry Parsing __init__.py recursion

Summaryinfo

A vulnerability was found in Django Software Foundation Django up to 5.2.16/6.0.7. It has been declared as problematic. Impacted is an unknown function of the file django/contrib/gis/geos/__init__.py of the component GEOS Geometry Parsing. Such manipulation leads to recursion. This vulnerability is traded as CVE-2026-15830. The attack may be launched remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in Django Software Foundation Django up to 5.2.16/6.0.7. It has been rated as problematic. Affected by this issue is some unknown processing of the file django/contrib/gis/geos/__init__.py of the component GEOS Geometry Parsing. The manipulation with an unknown input leads to a recursion vulnerability. Using CWE to declare the problem leads to CWE-674. The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack. Impacted is availability. CVE summarizes:

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.

The advisory is available at docs.djangoproject.com. This vulnerability is handled as CVE-2026-15830 since 07/15/2026. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 08/04/2026). This vulnerability is assigned to T1499 by the MITRE ATT&CK project.

Upgrading to version 5.2.17 or 6.0.8 eliminates this vulnerability.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

• Content Management System

Vendor

• Django Software Foundation

Name

• Django

Version

• 5.2.0
• 5.2.1
• 5.2.2
• 5.2.3
• 5.2.4
• 5.2.5
• 5.2.6
• 5.2.7
• 5.2.8
• 5.2.9
• 5.2.10
• 5.2.11
• 5.2.12
• 5.2.13
• 5.2.14
• 5.2.15
• 5.2.16
• 6.0.0
• 6.0.1
• 6.0.2
• 6.0.3
• 6.0.4
• 6.0.5
• 6.0.6
• 6.0.7

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion