Bug 2547363 - CVE-2026-87890 python-django6: Server-side request forgery via unvalidated bytes in spatial lookups [fedora-all]
Summary: CVE-2026-87890 python-django6: Server-side request forgery via unvalidated by...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: python-django6
Version: rawhide
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-17 01:05 UTC (History)
4 users (show)

Fixed In Version: python-django6-6.1.2-1.fc44
Clone Of:
Environment:
Last Closed: 2026-10-17 01:05:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Vladimir Vasilev 2026-10-07 10:27:28 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.

Comment 1 Fedora Update System 2026-10-08 10:18:46 UTC
FEDORA-2026-c221dbc190 (python-django6-6.1.2-1.fc45) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-c221dbc190

Comment 2 Fedora Update System 2026-10-08 10:18:55 UTC
FEDORA-2026-dbd9eb6961 (python-django6-6.1.2-1.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-dbd9eb6961

Comment 3 Fedora Update System 2026-10-09 02:08:20 UTC
FEDORA-2026-c221dbc190 has been pushed to the Fedora 45 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-c221dbc190`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-c221dbc190

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2026-10-09 02:30:12 UTC
FEDORA-2026-dbd9eb6961 has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-dbd9eb6961`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-dbd9eb6961

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2026-10-17 01:05:19 UTC
FEDORA-2026-dbd9eb6961 (python-django6-6.1.2-1.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.


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