CVE-2026-114582
Server-side request forgery via SpatialReference string input
An issue was discovered in Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19. `django.contrib.gis.gdal.SpatialReference` (and related `transform()` methods and `srs`/`srid` setters) do not restrict GDAL’s file and network access when parsing string input, which allows attackers to trigger server-side requests or local file reads via crafted spatial reference strings. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Adraca for reporting this issue.
Fixes and workarounds
Fix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: DSFFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: DSFFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: DSFFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: DSFAffected products and versions
| Product | Versions | Authority |
|---|---|---|
| Django djangoproject django
https://pypi.org/project/Django/ |
≥ 6.1; < 6.1.3 (affected, python) 6.1.3 (unaffected, python) ≥ 6.0; < 6.0.10 (affected, python) 6.0.10 (unaffected, python) ≥ 5.2; < 5.2.19 (affected, python) 5.2.19 (unaffected, python) Other versions: unaffected |
CNA: DSF |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 5.3 medium |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | CNA: DSF |
| 4.0 / 6.9 medium |
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N | CNA: DSF |
| 4.0 / 6.9 medium |
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X | NVD: 6a34fbeb-21d4-45e7-8e0a-62b95bc12c92 |
| 3.1 / 5.3 medium |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | NVD: 6a34fbeb-21d4-45e7-8e0a-62b95bc12c92 |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://docs.djangoproject.com/en/dev/releases/security/CNA: DSF · vendor-advisory
- https://groups.google.com/g/django-announceCNA: DSF · mailing-list
- https://github.com/django/django/commit/3a2ec4378b53c7b8ff5283ad7eba624ffa6f2b2fCNA: DSF · patch
- https://github.com/django/django/commit/a658355eb51feccbe90b5ca2e3b7f3543cd99e01CNA: DSF · patch
- https://github.com/django/django/commit/1c980729e53ef119d43a01d32ead30116c46cd36CNA: DSF · patch
- https://github.com/django/django/commit/8bda4d0db15f28828d8db000287562efae5ce063CNA: DSF · patch
- https://www.djangoproject.com/weblog/2026/nov/03/security-releases/CNA: DSF · vendor-advisory
- https://docs.djangoproject.com/en/dev/releases/security/6a34fbeb-21d4-45e7-8e0a-62b95bc12c92
- https://github.com/django/django/commit/1c980729e53ef119d43a01d32ead30116c46cd366a34fbeb-21d4-45e7-8e0a-62b95bc12c92
- https://github.com/django/django/commit/3a2ec4378b53c7b8ff5283ad7eba624ffa6f2b2f6a34fbeb-21d4-45e7-8e0a-62b95bc12c92
- https://github.com/django/django/commit/8bda4d0db15f28828d8db000287562efae5ce0636a34fbeb-21d4-45e7-8e0a-62b95bc12c92
- https://github.com/django/django/commit/a658355eb51feccbe90b5ca2e3b7f3543cd99e016a34fbeb-21d4-45e7-8e0a-62b95bc12c92
- https://groups.google.com/g/django-announce6a34fbeb-21d4-45e7-8e0a-62b95bc12c92
- https://www.djangoproject.com/weblog/2026/nov/03/security-releases/6a34fbeb-21d4-45e7-8e0a-62b95bc12c92
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.