Django GeoDjango spatial lookups allow file writes and outbound requests through GDAL raster parsing
Published 4 Aug 2026 · Updated 1 Oct 2026
Is your project on an affected django?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- <5.2.17
- Fixed in
- 5.2.17
pip install 'django>=5.2.17'- Affected
- >=6.0a1 <6.0.8
- Fixed in
- 6.0.8
pip install 'django>=6.0.8'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.
Is GHSA-wvqv-fj8w-qmhm in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected django, and gives you the command that fixes it.
More advisories for django
- MediumCVE-2026-15830Django GeoDjango vulnerable to denial of service through deeply nested geometry collections · 4 Aug 2026
- MediumCVE-2026-53878Django: DomainNameValidator permits newline characters that may enable HTTP header injection · 7 Jul 2026
- MediumCVE-2026-53877 Django: GDALRaster may over-read heap memory when constructed from bytes · 7 Jul 2026
- LowCVE-2026-48588Django: cache middleware may expose private responses when unrelated request cookies are present · 7 Jul 2026
- LowCVE-2026-8404Django: UpdateCacheMiddleware may disclose cached responses due to case-sensitive Cache-Control handling · 3 Jun 2026
- LowCVE-2026-48587Django: has_vary_header may expose cached responses when Vary values contain whitespace · 3 Jun 2026
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-15307
- Linkgithub.com/django/django/commit/115ffd0463a765ab1cc93de18e94b5459b8a300e
- Linkgithub.com/django/django/commit/208f80cb682868b584ed0a78f23e4ba6304212aa
- Linkgithub.com/django/django/commit/39b3e2d0c743a338def6c473086ebc06865e86b6
- Linkgithub.com/django/django/commit/f1949c1f9758947ade984c895ff16bef46f56520
- Linkdocs.djangoproject.com/en/dev/releases/security
- Packagegithub.com/django/django
- Linkgroups.google.com/g/django-announce
- Linkwww.djangoproject.com/weblog/2026/aug/04/security-releases
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.