Bug 2564003 (CVE-2026-111362) - CVE-2026-111362 django: Server-side request forgery via crs member of GeoJSON geometries
Summary: CVE-2026-111362 django: Server-side request forgery via crs member of GeoJSON...
Keywords:
Status: NEW
Alias: CVE-2026-111362
Deadline: 2026-11-03
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:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-10-30 13:24 UTC by OSIDB Bzimport
Modified: 2026-11-12 09:34 UTC (History)
48 users (show)

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


Attachments (Terms of Use)

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.


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