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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-15307: 1.13% estimated exploitation activity in the next 30 days; percentile 66.52 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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,…

Published by the source

4 Aug 2026, 18:31 UTC

Last modified by the source

30 Sep 2026, 23:25 UTC

Source last checked

26 Oct 2026, 13:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-wvqv-fj8w-qmhm

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-15307

Advisory: Django GeoDjango spatial lookups allow file writes and outbound requests through GDAL raster parsing
IDs: CVE-2026-15307, GHSA-wvqv-fj8w-qmhm
Record: https://patchnext.com/advisories/cve-2026-15307 (revision 1, source checked 26 Oct 2026, 13:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: django 6.0.8, 5.2.17. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI django: affected < 5.2.17; >= 6.0a1, < 6.0.8; fixed in 6.0.8, 5.2.17

## Suggested inspection (read-only)
- `python -m pip show django`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on django.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-wvqv-fj8w-qmhm (GitHub-reviewed advisory GHSA-wvqv-fj8w-qmhm lists affected ranges: PyPI django >=0 =6.0a1 <6.0.8)

Commands are suggestions: review each one before running it.