CVE-2026-15830
Last modified
CVE-2026-15830 is a medium-severity vulnerability rated 5.3/10 on the CVSS scale. 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.. EPSS estimates a 0.52% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Djangoproject | Django | < 5.2.17 |
| Djangoproject | Django | >= 6.0, < 6.0.8 |
References
- https://docs.djangoproject.com/en/dev/releases/security/Patch, Vendor Advisory
- https://groups.google.com/g/django-announceMailing List
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-15830?
How severe is CVE-2026-15830?
How do I fix CVE-2026-15830?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-15820The Builderall for WordPress plugin for WordPress is vulnera…6.4
- CVE-2026-15821The SureDash – Community, Courses & Member Dashboard plugin …6.4
- CVE-2026-15823The Builderall Cheetah For Wp plugin for WordPress is vulner…4.3
- CVE-2026-15826The User Profile Builder plugin for WordPress is vulnerable …9.8
- CVE-2026-15827The GutenKit Blocks plugin for WordPress is vulnerable to un…5.3
- CVE-2026-15829A SQL injection (CWE-89) and security boundary bypass (CWE-8…8.1
- CVE-2026-15831GitLab has remediated an issue in GitLab EE affecting all ve…4.3
- CVE-2026-1584A flaw was found in gnutls. A remote, unauthenticated attack…7.5
- CVE-2026-1585An unquoted Windows service executable path vulnerability in…8.4
- CVE-2026-1586A flaw has been found in Open5GS up to 2.7.5. Impacted is th…7.5
- CVE-2026-1587A vulnerability has been found in Open5GS up to 2.7.6. The a…7.5
- CVE-2026-1588A vulnerability was found in jishenghua jshERP up to 3.6. Th…2.7
Are you affected by CVE-2026-15830?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST