Server-side Request Forgery (SSRF) Affecting django package, versions [5.2a1, 5.2.19)[6.0a1, 6.0.10)[6.1a1, 6.1.3)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Server-side Request Forgery (SSRF) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-PYTHON-DJANGO-22200528
- published4 Nov 2026
- disclosed3 Nov 2026
- creditSubmersion Security Research Team
Introduced: 3 Nov 2026
NewCVE-2026-111362 (opens in a new tab)How to fix?
Upgrade Django to version 5.2.19, 6.0.10, 6.1.3 or higher.
Overview
Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) in GeoDjango's GeoJSON handling, reached through spatial-field lookups, the GeometryField form field, and the GEOSGeometry constructor. An attacker can make the server issue outbound network requests as the Django process user or read local files by submitting a GeoJSON geometry whose crs member references an external URL, which GDAL resolves. Exploitation requires a path that instantiates a geometry from untrusted input, and the DataSource and LayerMapping loaders are out of scope because they are intended for trusted data.