CVE-2026-15830
mediumPriorität · verfolgen · 0EPSS 0.011 · 66. PerzentilDEEUUSEPSS · bewertet 2026-10-26
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.
cvss
Technischer Schweregrad, 0–10. Eine Zeile je Quelle.
Basiswert 0–10 · höher = schwerwiegender · Vektor überfahren zum Auflösen⚠ Quellen uneinig · low–medium · 2.7–6.9
SSVC
Eine Handlungsentscheidung — aus Ausnutzung und Auswirkung.
schwächen
Die CWE-Schwächeklassen, zu denen dies gehört.
betroffene Produkte (20)
Betroffene Produkte und Versionsbereiche.
- Red Hat Ansible Automation Platform 2.5alle Versionencert_bundDEcpe:/a:redhat:ansible_automation_platform:2.5
- Red Hat Ansible Automation Platform 2.6alle Versionencert_bundDEcpe:/a:redhat:ansible_automation_platform:2.6
- Red Hat Ansible Automation Platform 2.7alle Versionencert_bundDEcpe:/a:redhat:ansible_automation_platform:2.7
Advisories (4)
Hersteller- und Ökosystem-Meldungen dazu.
- WID-SEC-W-2026-2649Django: Mehrere SchwachstellenDeutsch2026-08-04csaf · cert_bundDE
Ein Angreifer kann mehrere Schwachstellen in Django ausnutzen, um beliebigen Programmcode auszuführen, Daten zu manipulieren, Cross-Site-Scripting-Angriffe durchzuführen oder einen Denial-of-Service-Zustand auszulösen.
- GHSA-q238-5cxm-5c9hDjango GeoDjango vulnerable to denial of service through deeply nested geometry collections2026-08-04ghsa · osvUS
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.
- BIT-django-2026-15830Potential denial-of-service vulnerability via nested geometry collections2026-08-19vendor · osvUS
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.
- PYSEC-2026-37172026-08-04vendor · osvUS
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.
auch bekannt als (6)
Weitere Namen und Kennungen dieser Entität.
quellen
Welche Quellen diesen Datensatz belegen und wann.
Referenzen (25)
Externe Belege — Patches, Meldungen, Analysen.
- https://docs.djangoproject.com/en/dev/releases/security/cnnvd
- https://github.com/django/django/commit/6af5da31775417c610dbf9c3f1b5b8333d42daf6cnnvd
- https://github.com/django/django/commit/9e4a3f186b6b07b483bfd9195ea06734663fcd06cnnvd
- https://github.com/django/django/commit/ba80833fa656dd09660b97c4429331067db1b080cnnvd
- https://github.com/django/django/commit/d2e59b77fe18de318a8272c2a7bbc798d84d1d0dcnnvd
- https://groups.google.com/g/django-announcecnnvd
- https://www.djangoproject.com/weblog/2026/aug/04/security-releases/cnnvd
- https://docs.djangoproject.com/en/dev/releases/security/enisa_euvd
Angreifer nutzen Schwachstellen wie diese gegen im Internet exponierte Dienste aus. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.
Kostenloser Scan