CVE-2026-15830

Potential denial-of-service vulnerability via nested geometry collections

Published Aug 4, 2026 CVSS 4.0 · 6.9 Medium EPSS 1.1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability arises when deeply nested GEOMETRYCOLLECTION objects are parsed as well‑known text, well‑known binary, or hex‑encoded binary, causing the GEOS geometry library to recurse without bound and ultimately trigger a segmentation fault. This results in an application crash that can be used to deny service to users. The weakness is classified as unbounded recursion (CWE‑674) and missing input validation (CWE‑606).

Affected Systems

The affected product is Django, specifically the GeoDjango component. Versions prior to 5.2.18 in the 5.2 series and prior to 6.0.9 in the 6.0 series are impacted. Earlier Django releases such as 5.1.x, 5.0.x, and 4.2.x have not been evaluated but are suspected to be vulnerable as well.

Risk and Exploitability

The CVSS score of 6.9 indicates moderate severity. The EPSS score of < 1% indicates a very low, but non‑zero, likelihood of exploitation, meaning the vulnerability is typically not actively targeted, yet requires a specially crafted geometry object to trigger. The attack vector is likely remote via public API or web forms that process geometry data, leading to a denial‑of‑service condition through application crash. The vulnerability is not listed in CISA’s KEV catalog, but the impact of a service crash for any critical application should not be underestimated.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Django to version 5.2.18 or later, or to version 6.0.9 or later to apply the official fix for the recursion issue
  • If upgrading is temporarily infeasible, restrict or validate incoming geometry data by capping maximum nesting depth to prevent the parser from reaching the recursion limit
  • Monitor application logs for crashes or segmentation faults related to GEOS geometry parsing and take corrective action promptly

Generated by OpenCVE AI on October 8, 2026 at 13:47 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-q238-5cxm-5c9h Django GeoDjango vulnerable to denial of service through deeply nested geometry collections
History
Type Values Removed Values Added
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. 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.
References
Type Values Removed Values Added
CPEs cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:*
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Djangoproject
Djangoproject django
Vendors & Products Djangoproject
Djangoproject django
Type Values Removed Values Added
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.
Title Potential denial-of-service vulnerability via nested geometry collections
Weaknesses CWE-674
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}

cvssV4_0

{'score': 6.9, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-606

    Unchecked Input for Loop Condition

  • CWE-674

    Uncontrolled Recursion

Sources

Status
PUBLISHED
Assigner
DSF
Published
Updated
Oct 8, 2026, 10:58 AM
Reserved
Jul 15, 2026, 3:01 PM
Status
Modified
Published
Aug 4, 2026, 5:16 PM
Modified
Oct 24, 2026, 4:10 PM
Severity
Moderate
Public date
Aug 4, 2026, 3:48 PM