CVE-2026-15307: Django GeoDjango spatial lookups allow file writes and outbound requests through GDAL raster parsing
High CVSS 8.8
- OSV id
- GHSA-wvqv-fj8w-qmhm
- Also known as
- BIT-django-2026-15307, CVE-2026-15307, PYSEC-2026-4035
- Published
- Last modified
Affected packages
Versions we track that it affects: django 5.0.6, django 4.2.11; django 5.0.6, django 4.2.11
How to fix it
django (PyPI)
Upgrade django to 5.2.17 or later.
# in requirements.txt: change the line to django==5.2.17
pip install -r requirements.txt
- If it is an indirect dependency, upgrade the package that depends on it, or add a minimum version constraint for it (e.g. in constraints.txt, or as a dependency in pyproject.toml).
- Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
django (PyPI)
Upgrade django to 6.0.8 or later.
# in requirements.txt: change the line to django==6.0.8
pip install -r requirements.txt
- If it is an indirect dependency, upgrade the package that depends on it, or add a minimum version constraint for it (e.g. in constraints.txt, or as a dependency in pyproject.toml).
- Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
Not sure whether your project uses an affected version? Check your lockfile below for free.
Details
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.
References
- GHSA-wvqv-fj8w-qmhm on OSV.dev
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-15307
- Web: https://github.com/django/django/commit/115ffd0463a765ab1cc93de18e94b5459b8a300e
- Web: https://github.com/django/django/commit/208f80cb682868b584ed0a78f23e4ba6304212aa
- Web: https://github.com/django/django/commit/39b3e2d0c743a338def6c473086ebc06865e86b6
- Web: https://github.com/django/django/commit/f1949c1f9758947ade984c895ff16bef46f56520
- Web: https://docs.djangoproject.com/en/dev/releases/security
- Package: https://github.com/django/django
- Web: https://groups.google.com/g/django-announce
- Web: https://www.djangoproject.com/weblog/2026/aug/04/security-releases
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.