PatchSiren cyber security CVE debrief
CVE-2026-15830 Djangoproject CVE debrief
A potential denial-of-service vulnerability was discovered in GeoDjango's `GEOSGeometry` when parsing deeply nested `GEOMETRYCOLLECTION` objects supplied as well-known text (WKT), well-known binary (WKB), or hex-encoded WKB. This issue affects Django versions 5.2 before 5.2.17 and 6.0 before 6.0.8. The vulnerability is caused by 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. The vulnerability was reported by Andrew MacPherson and kimchunbok_. Official patches are available for affected Django versions. Further verification is recommended to confirm affected scope and severity.
- Vendor
- Djangoproject
- Product
- Django
- CVSS
- MEDIUM 6.9
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-04
- Original CVE updated
- 2026-08-18
- Advisory published
- 2026-08-04
- Advisory updated
- 2026-08-18
Who should care
Developers and administrators using GeoDjango functionality in Django versions 5.2 before 5.2.17 and 6.0 before 6.0.8 should be aware of this potential denial-of-service vulnerability and take steps to mitigate it. Affected operators, platforms, vulnerability-management, and security teams should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
Technical summary
The vulnerability is caused by unbounded recursion and a segmentation fault in the underlying GEOS library when parsing deeply nested GEOMETRYCOLLECTION objects supplied as well-known text (WKT), well-known binary (WKB), or hex-encoded WKB. Spatial field lookups and the django.contrib.gis.forms.GeometryField form field are also affected. This issue affects Django versions 5.2 before 5.2.17 and 6.0 before 6.0.8.
Defensive priority
Medium priority due to potential denial-of-service vulnerability in widely used GeoDjango functionality.
Recommended defensive actions
- Apply official patches for affected Django versions
- Review and update GeoDjango usage to prevent potential denial-of-service
- Monitor for and address potential exploitation attempts
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
- Review compensating controls for exposed systems while remediation is scheduled and verified.
- Check relevant monitoring, detection, and logs for exposed assets that need extra review.
- Track exceptions, retest remediated assets, and close the item only after evidence is documented.
Evidence notes
The vulnerability was reported by Andrew MacPherson and kimchunbok_. Official patches are available for affected Django versions. Further verification is recommended to confirm affected scope and severity. Defenders should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-15830 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-15830
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-15830 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-15830
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Mitigation or vendor reference
Unverified legacy reference
URL: https://docs.djangoproject.com/en/dev/releases/security/
6a34fbeb-21d4-45e7-8e0a-62b95bc12c92 - Patch, Vendor Advisory
-
Mitigation or vendor reference
Unverified legacy reference
URL: https://github.com/django/django/commit/6af5da31775417c610dbf9c3f1b5b8333d42daf6
6a34fbeb-21d4-45e7-8e0a-62b95bc12c92 - Patch
-
Mitigation or vendor reference
Unverified legacy reference
URL: https://github.com/django/django/commit/9e4a3f186b6b07b483bfd9195ea06734663fcd06
6a34fbeb-21d4-45e7-8e0a-62b95bc12c92 - Patch
-
Mitigation or vendor reference
Unverified legacy reference
URL: https://github.com/django/django/commit/ba80833fa656dd09660b97c4429331067db1b080
6a34fbeb-21d4-45e7-8e0a-62b95bc12c92 - Patch
-
Mitigation or vendor reference
Unverified legacy reference
URL: https://github.com/django/django/commit/d2e59b77fe18de318a8272c2a7bbc798d84d1d0d
6a34fbeb-21d4-45e7-8e0a-62b95bc12c92 - Patch
-
Source reference
Unverified legacy reference
URL: https://groups.google.com/g/django-announce
6a34fbeb-21d4-45e7-8e0a-62b95bc12c92 - Mailing List
-
Mitigation or vendor reference
Unverified legacy reference
URL: https://www.djangoproject.com/weblog/2026/aug/04/security-releases/
6a34fbeb-21d4-45e7-8e0a-62b95bc12c92 - Vendor Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.