CVE-2026-15830: CWE-674: Uncontrolled Recursion in djangoproject Django
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.
AI Analysis
Technical Summary
This vulnerability in Django's GeoDjango module arises from uncontrolled recursion triggered by deeply nested GEOMETRYCOLLECTION objects supplied as WKT, WKB, or hex-encoded WKB. The recursion causes a segmentation fault in the underlying GEOS library, resulting in a denial-of-service condition. The issue affects spatial field lookups and the GeometryField form field. It impacts Django versions 5.2 prior to 5.2.17 and 6.0 prior to 6.0.8. Earlier unsupported versions such as 5.1.x, 5.0.x, and 4.2.x were not evaluated but may also be vulnerable. The vulnerability is tracked as CWE-674 (Uncontrolled Recursion).
Potential Impact
The vulnerability allows an attacker to cause a denial-of-service by triggering a segmentation fault through crafted deeply nested geometry collections. There is no impact on confidentiality or integrity reported. The attack vector is network-based with no privileges or user interaction required.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or remediation level has been published at this time. Users should monitor Django project advisories for updates and consider mitigating exposure to untrusted spatial data inputs until a fix is available.
CVE-2026-15830: CWE-674: Uncontrolled Recursion in djangoproject Django
Description
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.
CVSS v3.1
Score 5.3medium
Affected software
djangoproject
Django
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability in Django's GeoDjango module arises from uncontrolled recursion triggered by deeply nested GEOMETRYCOLLECTION objects supplied as WKT, WKB, or hex-encoded WKB. The recursion causes a segmentation fault in the underlying GEOS library, resulting in a denial-of-service condition. The issue affects spatial field lookups and the GeometryField form field. It impacts Django versions 5.2 prior to 5.2.17 and 6.0 prior to 6.0.8. Earlier unsupported versions such as 5.1.x, 5.0.x, and 4.2.x were not evaluated but may also be vulnerable. The vulnerability is tracked as CWE-674 (Uncontrolled Recursion).
Potential Impact
The vulnerability allows an attacker to cause a denial-of-service by triggering a segmentation fault through crafted deeply nested geometry collections. There is no impact on confidentiality or integrity reported. The attack vector is network-based with no privileges or user interaction required.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or remediation level has been published at this time. Users should monitor Django project advisories for updates and consider mitigating exposure to untrusted spatial data inputs until a fix is available.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- DSF
- Date Reserved
- 2026-07-15T15:01:48.803Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a72133ebf8831d5391ad45a
Added to database: 08/04/2026, 16:28:46 UTC
Last enriched: 08/11/2026, 18:13:38 UTC
Last updated: 09/18/2026, 10:01:29 UTC
Views: 50
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.