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

Advisory record · `GHSA-wvqv-fj8w-qmhm`

- **Identifiers:** `GHSA-wvqv-fj8w-qmhm` · `BIT-django-2026-15307` · `CVE-2026-15307` · `PYSEC-2026-4035`
- **State:** Confirmed
- **Severity:** CVSS 8.7 High
- **Critical:** No
- **Weakness (CWE):** [CWE-73](https://cwe.mitre.org/data/definitions/73.html) · [CWE-918](https://cwe.mitre.org/data/definitions/918.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md) · [Server-side request forgery (SSRF)](https://agentprime.io/advisories/tag/ssrf.md)
- **Published:** 4 Aug 2026
- **Updated:** 1 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 4 Aug 2026, 18:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `django` (PyPI): affected `<5.2.17 || >=6.0a1, <6.0.8`; fixed in `5.2.17`, `6.0.8`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Django 5.2 before 5.2.17 and Django 6.0 before 6.0.8 are vulnerable. An attacker who can supply a value to a spatial lookup on a GeometryField or RasterField, such as a staff user with view permission filtering through the admin changelist, can cause files to be written through GDAL or trigger outbound network requests. Writing a file to a location the application later imports can lead to remote code execution. Upgrade to Django 5.2.17 or 6.0.8. Earlier unsupported series were not evaluated and may also be affected.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.7 High, CVSS 4.0: `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`, from CNA (DSF)

- **CISA KEV:** Not listed.
- **EPSS:** 0.011, the 66th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:09 UTC: First seen by agentprime
- 31 Oct 2026, 14:09 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-wvqv-fj8w-qmhm)

## Sources

- [GitHub Advisory Database: GHSA-wvqv-fj8w-qmhm](https://github.com/advisories/GHSA-wvqv-fj8w-qmhm)
- [OSV: GHSA-wvqv-fj8w-qmhm](https://osv.dev/vulnerability/GHSA-wvqv-fj8w-qmhm)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-15307>
- <https://github.com/django/django/commit/115ffd0463a765ab1cc93de18e94b5459b8a300e>
- <https://github.com/django/django/commit/208f80cb682868b584ed0a78f23e4ba6304212aa>
- <https://github.com/django/django/commit/39b3e2d0c743a338def6c473086ebc06865e86b6>
- <https://github.com/django/django/commit/f1949c1f9758947ade984c895ff16bef46f56520>
- <https://docs.djangoproject.com/en/dev/releases/security>
- <https://github.com/django/django>
- <https://groups.google.com/g/django-announce>
- <https://www.djangoproject.com/weblog/2026/aug/04/security-releases>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-wvqv-fj8w-qmhm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-wvqv-fj8w-qmhm/>. Everything for agents: <https://agentprime.io/llms.txt>.