Server-side Request Forgery (SSRF) Affecting django package, versions [,5.2.18)[6.0a1,6.0.9)[6.1a1,6.1.2)
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-20825029
- published11 Oct 2026
- disclosed8 Oct 2026
- creditsicksec
Introduced: 8 Oct 2026
NewCVE-2026-87890 (opens in a new tab)How to fix?
Upgrade Django to version 5.2.18, 6.0.9, 6.1.2 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) via the spatial lookup handling in django/contrib/gis/db/models/fields.py and django/contrib/gis/gdal/raster/source.py. An attacker can cause the Django process to make network requests by supplying attacker-controlled bytes to a raster lookup that is processed as a GDAL raster input. The vulnerable code accepts bytes in lookup contexts without requiring explicit GDALRaster wrapping, and GDAL can interpret that data as a VRT document referencing external raster sources. This lets an attacker trigger outbound file or network access while the lookup is being prepared, exposing the application to unintended requests made as the Django process user.