Bug 2547364 - CVE-2026-87890 python-django4.2: Server-side request forgery via unvalidated bytes in spatial lookups [epel-all]
Summary: CVE-2026-87890 python-django4.2: Server-side request forgery via unvalidated ...
Keywords:
Status: NEW
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-django4.2
Version: epel10
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Michel Lind
QA Contact:
URL:
Whiteboard: {"flaws": ["e15a3994-53ca-4220-8e77-1...
Depends On:
Blocks: CVE-2026-87890
TreeView+ depends on / blocked
 
Reported: 2026-10-07 10:27 UTC by Vladimir Vasilev
Modified: 2026-10-07 10:27 UTC (History)
2 users (show)

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


Attachments (Terms of Use)

Description Vladimir Vasilev 2026-10-07 10:27:38 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

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.