{"id":"CVE-2026-15307","published":"2026-08-04T17:16:46.127","lastModified":"2026-08-05T05:16:46.480","description":"An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8.\nGeoDjango spatial lookups optimistically parse the right-hand-side value as a raster by passing it to the `django.contrib.gis.gdal.GDALRaster` constructor. Any value used in a spatial lookup against a `GeometryField` or `RasterField` reaches this constructor, including untrusted input, for example a spatial-field filter submitted through the Django admin changelist query string by a staff user with view permission. A `dict`, or a `str` holding its JSON representation, is opened in write mode regardless of the constructor's `write=False` default, allowing a file with an attacker-chosen name and contents to be written through a file-backed GDAL driver. Any other `str` is treated as a datasource, allowing an outbound network request through a GDAL virtual filesystem handler. Writing a file to a location later imported by the application can result in remote code execution.\nEarlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected.\nDjango would like to thank Bence Nagy, localhost-detect, and kimchunbok_ for reporting this issue.","cvssScore":8.8,"cvssSeverity":"HIGH","cvssVector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","cwes":["CWE-73","CWE-918"],"vendors":[],"products":[],"references":[{"url":"https://docs.djangoproject.com/en/dev/releases/security/","tags":[]},{"url":"https://github.com/django/django/commit/115ffd0463a765ab1cc93de18e94b5459b8a300e","tags":[]},{"url":"https://github.com/django/django/commit/208f80cb682868b584ed0a78f23e4ba6304212aa","tags":[]},{"url":"https://github.com/django/django/commit/39b3e2d0c743a338def6c473086ebc06865e86b6","tags":[]},{"url":"https://github.com/django/django/commit/f1949c1f9758947ade984c895ff16bef46f56520","tags":[]},{"url":"https://groups.google.com/g/django-announce","tags":[]},{"url":"https://www.djangoproject.com/weblog/2026/aug/04/security-releases/","tags":[]}],"exploitRefs":[{"url":"https://github.com/django/django/commit/115ffd0463a765ab1cc93de18e94b5459b8a300e","tags":[]},{"url":"https://github.com/django/django/commit/208f80cb682868b584ed0a78f23e4ba6304212aa","tags":[]},{"url":"https://github.com/django/django/commit/39b3e2d0c743a338def6c473086ebc06865e86b6","tags":[]},{"url":"https://github.com/django/django/commit/f1949c1f9758947ade984c895ff16bef46f56520","tags":[]}],"hasPoc":true,"ai":{"summary":"The flaw allows untrusted input to be used in spatial lookups, potentially leading to file writes and network requests that could result in remote code execution.","exploitability":"Exploitation requires a staff user with view permission and access to the Django admin changelist query string. Precondition is the use of unsupported Django series or versions before specified patches.","blast_radius":"If exploited, this can lead to significant damage including data loss, unauthorized code execution, and network breaches in real-world applications.","remediation":"Update affected Django installations to version 5.2.17 or later, or 6.0.8 or later, immediately.","tags":["rce","web","django","gis","security"],"model":"qwen2.5:7b-instruct","analyzedAt":"2026-08-11T06:46:24.041Z"}}