CVE-2026-15307
GeoDjango spatial lookup parsing allows file write or datasource fetch leading to RCE.
Is CVE-2026-15307 being exploited?
Not confirmed. CVE-2026-15307 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.90% probability of exploitation in the next 30 days.
How severe is CVE-2026-15307?
CVE-2026-15307 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-15307?
Yes. A fix has been recorded for CVE-2026-15307. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-15307 affect?
CVE-2026-15307 affects Django 6.0 < 6.0.8, Django 5.2 < 5.2.17, GeoDjango spatial lookups, Possibly earlier unsupported 4.2/5.1/5.0 series. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-15307?
Upgrade to Django 6.0.8 or 5.2.17 ASAP; restrict GeoDjango access and validate spatial inputs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution via crafted raster/datasource in GeoDjango spatial lookups; attackers can write files or trigger outbound fetches to achieve RCE.
Immediate action required
- affected>= 6.0 and < 6.0.8
- affected>= 5.2 and < 5.2.17
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.