AIKIDO-2026-197487
django is vulnerable to Server-Side Request Forgery (SSRF)
53
Medium Risk
This Affects:
djangoTL;DR
Spatial lookups pass bytes values to GDALRaster from BaseSpatialField.get_prep_value in django/contrib/gis/db/models/fields.py. GDALRaster writes those bytes to GDAL's in-memory virtual filesystem and opens them, so a buffer containing a VRT document can reference an external raster source and cause the Django process to make a network request while preparing the lookup. GDALRaster.check_raster_lookup_value rejects dict and str inputs on releases that include that guard, and still allows bytes. The fix rejects bytes in the lookup guard and in the geometry fallback, while still accepting valid hexadecimal geometry bytes.
Who does this affect?
You are affected if you are using a version that falls within the vulnerable range and your application passes user-controllable bytes into a GeoDjango spatial lookup that can reach GDALRaster.
Background info
django is vulnerable to Server-Side Request Forgery (SSRF) in versions 6.1 - 6.1.1, 6.0 - 6.0.8 and 5.2 - 5.2.17.
How to fix this
Upgrade the django library to the patch version.
Links
Fix Commits
github.com/django/django/commit/4e77ef1e69c94780006b82795aa7db101996c3afgithub.com/django/django/commit/a2347fe8234a1831d56c875acc0ea51e0742957cgithub.com/django/django/commit/dd0558d1617619e0d66163675ef02135d0f54e5fgithub.com/django/django/commit/ebcb13b327301f28cbc6cd5e4988a719f00575aaOther
djangoproject.com/weblog/2026/oct/06/security-releases/docs.djangoproject.com/en/dev/releases/security/groups.google.com/g/django-announce
Are You Affected?
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.