All vulnerabilities
CVE-2026-15307BIT-django-2026-15307GHSA-wvqv-fj8w-qmhmPYSEC-2026-4035

Django GeoDjango spatial lookups allow file writes and outbound requests through GDAL raster parsing

djangoproject DjangopipFrameworks
Open in ThreatlineRecord JSON
CVSS
8.7High
ExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)1.13%Chance of exploitation activity in the next 30 days, higher than 66% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed in5.2.17Also 6.0.8GitHub
Published4 Aug 2026Updated 1 Oct 2026CVE List

What fixes it

  • 5.2.17Django, pipGitHub
  • 6.0.8Django, pipGitHub
  • 6.0.8DjangoCVE List
  • 5.2.17DjangoCVE List
  • 5.2.17django, PyPIOSVpip install "django>=5.2.17"
  • 6.0.8django, PyPIOSVpip install "django>=6.0.8"

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

Description

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.

Text from GitHub Advisory Database

Affected versions 69

  • Django, pip< 5.2.17GitHub
  • Django, pip>= 6.0a1, < 6.0.8GitHub
  • Djangoaffected: 6.0 before 6.0.8CVE List
  • Djangounaffected: 6.0.8CVE List
  • Djangoaffected: 5.2 before 5.2.17CVE List
  • Djangounaffected: 5.2.17CVE List
  • django, PyPIfrom first release, fixed in 5.2.17OSV
  • django, PyPI1.0.1OSV
  • django, PyPI1.0.2OSV
  • django, PyPI1.0.3OSV
  • django, PyPI1.0.4OSV
  • django, PyPI1.1OSV
  • django, PyPI1.1.1OSV
  • django, PyPI1.1.2OSV
  • django, PyPI1.1.3OSV
  • django, PyPI1.1.4OSV
  • django, PyPI1.10OSV
  • django, PyPI1.10.1OSV
  • django, PyPI1.10.2OSV
  • django, PyPI1.10.3OSV
  • django, PyPI1.10.4OSV
  • django, PyPI1.10.5OSV
  • django, PyPI1.10.6OSV
  • django, PyPI1.10.7OSV
  • django, PyPI1.10.8OSV
  • django, PyPI1.10a1OSV
  • django, PyPI1.10b1OSV
  • django, PyPI1.10rc1OSV
  • django, PyPI1.11OSV
  • django, PyPI1.11.1OSV
  • django, PyPI1.11.10OSV
  • django, PyPI1.11.11OSV
  • django, PyPI1.11.12OSV
  • django, PyPI1.11.13OSV
  • django, PyPI1.11.14OSV
  • django, PyPI1.11.15OSV
  • django, PyPI1.11.16OSV
  • django, PyPI1.11.17OSV
  • django, PyPI1.11.18OSV
  • django, PyPI1.11.2OSV
  • django, PyPI1.11.20OSV
  • django, PyPI1.11.21OSV
  • django, PyPI1.11.22OSV
  • django, PyPI1.11.23OSV
  • django, PyPI1.11.24OSV
  • django, PyPI1.11.25OSV
  • django, PyPI1.11.26OSV
  • django, PyPI1.11.27OSV
  • django, PyPI1.11.28OSV
  • django, PyPI1.11.29OSV
  • django, PyPI1.11.3OSV
  • django, PyPI1.11.4OSV
  • django, PyPI1.11.5OSV
  • django, PyPI1.11.6OSV
  • django, PyPI1.11.7OSV
  • django, PyPI1.11.8OSV
  • django, PyPI1.11.9OSV
  • django, PyPIfrom 6.0a1, fixed in 6.0.8OSV
  • django, PyPI6.0OSV
  • django, PyPI6.0.1OSV
  • django, PyPI6.0.2OSV
  • django, PyPI6.0.3OSV
  • django, PyPI6.0.4OSV
  • django, PyPI6.0.5OSV
  • django, PyPI6.0.6OSV
  • django, PyPI6.0.7OSV
  • django, PyPI6.0a1OSV
  • django, PyPI6.0b1OSV
  • django, PyPI6.0rc1OSV

References 11