Loading vulnerability…
CVE-2026-15307 affects GeoDjango spatial lookups in Django 5.2 before 5.2.17 and Django 6.0 before 6.0.8. Right-hand-side values supplied to lookups against GeometryField or RasterField are passed to django.contrib.gis.gdal.GDALRaster for optimistic raster parsing. Dictionary values and strings containing their JSON representation are opened in write mode despite the constructor's write=False default, permitting attacker-chosen file names and contents through a file-backed GDAL driver. Other strings are interpreted as datasources and can trigger outbound requests through GDAL virtual filesystem handlers. An attacker-written file subsequently imported by the application can lead to remote code execution. Django admin changelist spatial filters expose this behavior to staff users with view permission on registered models containing spatial fields. Unsupported Django series, including 5.1.x, 5.0.x, and 4.2.x, were not evaluated and may also be affected.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
33 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A network-accessible vulnerability requiring low privileges and no user interaction, with high confidentiality, integrity, and availability impacts according to the supplied CVSS vectors. The content does not identify the affected product or underlying flaw. A patch publication date of October 2, 2026 is listed.
A vulnerability in GeoDjango affects Django 5.2 before 5.2.17 and 6.0 before 6.0.8. Spatial lookups against GeometryField or RasterField can pass untrusted input to GDALRaster. Dictionary or JSON-string input can trigger file writes despite the write=False default; other strings can trigger outbound network requests through GDAL virtual filesystem handlers. File writes to application-imported locations can lead to remote code execution. One described attack path requires a Django admin staff user with view permission. Unsupported Django releases were not evaluated and may also be affected. The package advisory recommends upgrading authentik-2026.2 and related packages to 2026.2.7-r3 or later.
A vulnerability addressed by Fedora advisory 2026-6b28b4e483 affecting the python-django5 package on Fedora 43. The provided CVSS vector indicates network-reachable impact requiring low privileges, with high confidentiality, integrity, and availability impact.
A vulnerability addressed by a Fedora 44 update for the python-django5 package. The content provides a CVSS v3 score vector indicating network attackability with low complexity and low privileges required, with high impact to confidentiality, integrity, and availability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.