Bug 2564003 (CVE-2026-111362)

Summary:	CVE-2026-111362 django: Server-side request forgery via crs member of GeoJSON geometries
Product:	[Other] Security Response	Reporter:	OSIDB Bzimport <bzimport>
Component:	vulnerability	Assignee:	Product Security <prodsec-ir-bot>
Status:	NEW ---	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	anthomas, brasmith, cmyers, cochase, dnakabaa, dranck, dschmidt, eglynn, ehelms, ggainey, jjoyce, jlanda, jmitchel, jpasqual, jpretori, jschluet, juwatts, jwong, kaycoth, kshier, lblicha, lbrazdil, lcouzens, lhh, mburns, mdellweg, mgarciac, mhulan, mminar, nmoumoul, ogajduse, omaciel, osousa, pcreech, rbiba, rbobbitt, rchan, security-response-team, simaishi, smallamp, sskracic, stcannon, tguha, tmalecek, tpfromme, ttakamiy, yguenane, zhunting
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:	A flaw was found in Django. When processing geographic data in GeoJSON format, the application fails to restrict external Coordinate Reference System (CRS) definitions. A remote attacker can exploit this vulnerability by submitting specially crafted geometric data referencing external resources, resulting in Server-Side Request Forgery (SSRF) and information disclosure. Successful exploitation allows the attacker to force the server to initiate unintended network requests or read local files with the privileges of the application process.	Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Deadline:	2026-11-03

Description OSIDB Bzimport 2026-10-30 13:24:10 UTC

CVE-2026-111362: Server-side request forgery via crs member of GeoJSON geometries

Earlier versions of the [GeoJSON spec](https://www.rfc-editor.org/info/rfc7946/#section-4)
allowed specifying a coordinate reference system (CRS) by URL. Since GDAL still resolves these
URLs, any validation, save, or query path where a geometry is instantiated from
user input allowed an attacker to submit a malicious CRS that would make a
network request as the Django process user, or read a file, or both.

Lookups against spatial fields, the `GeometryField` form field, and `GEOSGeometry` now
reject GeoJSON geometries with CRS references to external resources. The `DataSource` and
`LayerMapping` utilities for loading trusted data continue to accept these values.

This issue has severity "moderate" according to the [Django Security Policy](https://docs.djangoproject.com/en/dev/internals/security/#security-issue-severity-levels).

Thanks to Submersion Security Research Team for the report.