The vulnerability arises from GeoDjango spatial lookups parsing the right-hand-side value as a raster by passing it to the django.contrib.gis.gdal.GDALRaster constructor. Untrusted input, such as spatial-field filters submitted via the Django admin changelist query string, can cause a dict or JSON string to be opened in write mode, allowing file creation with attacker-controlled names and contents via a file-backed GDAL driver. Other string inputs are treated as datasources, enabling outbound network requests through a GDAL virtual filesystem handler. Writing files to locations later imported by the application can result in remote code execution. Affected versions include Django 5.2 prior to 5.2.17 and 6.0 prior to 6.0.8. Earlier unsupported versions may also be vulnerable. The CVSS v3.1 score is 8.8 (high severity) with network attack vector, low attack complexity, requiring low privileges but no user interaction, and impacts confidentiality, integrity, and availability.

Successful exploitation allows an attacker with staff view permissions to write files with arbitrary names and contents on the server or trigger outbound network requests, potentially leading to remote code execution. This compromises confidentiality, integrity, and availability of the affected system. The vulnerability affects the GeoDjango component when processing spatial lookups against GeometryField or RasterField, exposing a critical risk in applications using these features.

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, restrict staff user permissions to limit access to spatial-field filters and avoid using untrusted input in spatial lookups. Monitor vendor channels for updates and apply patches promptly once available.