Django Software Foundation up to 5.2.16/6.0.7 Spatial Lookup gdal.py django.contrib.gis.gdal.GDALRaster.__init__ right-hand-side unrestricted upload

Summaryinfo

A vulnerability was found in Django Software Foundation Django up to 5.2.16/6.0.7 and classified as critical. This vulnerability affects the function django.contrib.gis.gdal.GDALRaster.__init__ of the file django/contrib/gis/gdal/gdal.py of the component Spatial Lookup. The manipulation of the argument right-hand-side results in unrestricted upload. This vulnerability is reported as CVE-2026-15307. The attack can be launched remotely. No exploit exists.

Detailsinfo

A vulnerability was found in Django Software Foundation Django up to 5.2.16/6.0.7. It has been classified as critical. Affected is the function django.contrib.gis.gdal.GDALRaster.__init__ of the file django/contrib/gis/gdal/gdal.py of the component Spatial Lookup. The manipulation of the argument right-hand-side with an unknown input leads to a unrestricted upload vulnerability. CWE is classifying the issue as CWE-434. The product allows the attacker to upload or transfer files of dangerous types that can be automatically processed within the product's environment. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. GeoDjango 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. 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 Bence Nagy, localhost-detect, and kimchunbok_ for reporting this issue.

The advisory is shared for download at docs.djangoproject.com. This vulnerability is traded as CVE-2026-15307 since 07/09/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 08/04/2026). The MITRE ATT&CK project declares the attack technique as T1608.002.

Upgrading to version 5.2.17 or 6.0.8 eliminates this vulnerability.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Type

• Content Management System

Vendor

• Django Software Foundation

Name

• Django

Version

• 5.2.0
• 5.2.1
• 5.2.2
• 5.2.3
• 5.2.4
• 5.2.5
• 5.2.6
• 5.2.7
• 5.2.8
• 5.2.9
• 5.2.10
• 5.2.11
• 5.2.12
• 5.2.13
• 5.2.14
• 5.2.15
• 5.2.16
• 6.0.0
• 6.0.1
• 6.0.2
• 6.0.3
• 6.0.4
• 6.0.5
• 6.0.6
• 6.0.7

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion