Bug 2544149 (CVE-2026-87890) - CVE-2026-87890 django: Server-side request forgery via unvalidated bytes in spatial lookups
Summary: CVE-2026-87890 django: Server-side request forgery via unvalidated bytes in s...
Keywords:
Status: NEW
Alias: CVE-2026-87890
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2547364 2547363 2547365
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-30 17:22 UTC by OSIDB Bzimport
Modified: 2026-10-07 10:27 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-30 17:22:10 UTC
A flaw was found in Django's GIS support. Spatial lookups accepted raster values supplied as raw bytes without requiring them to first be wrapped in django.contrib.gis.gdal.GDALRaster. Because such values are opened through GDAL's in-memory virtual filesystem, a crafted value could contain a VRT document referencing an external raster source, causing GDAL to issue outbound network requests as the Django process user while preparing the lookup. An application that passes attacker-controlled bytes directly into a spatial lookup could therefore be induced to make server-side requests to attacker-chosen hosts. This issue was overlooked in the fix for CVE-2026-15307. It is a backward-incompatible fix: raster values provided as bytes must now be explicitly wrapped in GDALRaster before use in spatial lookups, though byte values representing valid hexadecimal geometries remain accepted.


Note You need to log in before you can comment on or make changes to this bug.