The Django team shipped security releases 6.1.3, 6.0.10 and 5.2.19 on November 3, 2026. Together they patch six CVEs that touch file uploads, page caching, the admin site and the GeoDjango spatial toolkit.
Five of the issues are rated low under the Django security policy, and one is rated moderate. The moderate bug lets an attacker make a Django site fetch a URL or read a local file through GeoJSON input, so teams that run GeoDjango should treat this update as urgent. Everyone else should still plan to upgrade soon.
What Changed in These Releases
All three supported release lines get the same set of fixes, and the patches were also merged into the main development branch. The password hash fix applies only to the 6.1 and 6.0 lines, because the 5.2 branch is not affected by that problem.
- CVE-2026-108147 (low): base64-encoded parts in multipart uploads could be held fully in memory, ignoring the FILE_UPLOAD_MAX_MEMORY_SIZE limit.
- CVE-2026-111211 (low): GeometryField and its widgets wrote invalid user input to logs without escaping control characters.
- CVE-2026-111362 (moderate): a GeoJSON geometry could carry a crs member pointing to an outside resource, and GDAL would resolve it.
- CVE-2026-113593 (low): the cache middleware and cache_page() treated a missing Vary header and an empty one as the same request.
- CVE-2026-113733 (low): admin users with only view rights on some user models could see the full password hash.
- CVE-2026-114582 (low): SpatialReference handed string input to GDAL, which can follow URLs and open files.
The Two GeoDjango SSRF Issues
Older versions of the GeoJSON format let a geometry name its coordinate reference system by URL. GDAL still follows those links, so any form, lookup or save that built a geometry from user data could trigger an outbound request or a file read as the Django process user.
After the fix, spatial field lookups, the GeometryField form field and GEOSGeometry refuse GeoJSON that points its CRS at an external resource. The DataSource and LayerMapping helpers still accept such values, because they are meant for loading data you already trust.
The second SSRF issue sits in SpatialReference and in the transform and srs methods of several geometry and raster classes. On GDAL 3.9 or newer, Django now turns off network and file access when it parses string references. File paths and URLs are no longer valid inputs, and references using the DICT: prefix are blocked on every GDAL version.
Caching, Uploads and Admin Fixes
The caching bug matters for sites that vary responses by a header such as a cookie or language. A page cached for a request that left the header out could be returned to a request that sent it blank, or the other way round, which could leak private content.
Cache keys now tell the two cases apart, in line with RFC 9111. One side effect is that some existing cache entries will stop matching and will be rebuilt on the next request, so expect a short rise in cache misses after you deploy.
The upload fix closes a memory exhaustion path in MultiPartParser. The admin fix stops showing the full password hash to staff who can only view a user model, a case that appeared with custom models outside AUTH_USER_MODEL or with multi-table inheritance.
What It Means for Developers
For most projects this is a routine patch upgrade with no code changes needed. The main exception is GeoDjango code that builds a SpatialReference from a string path or URL, since that input is now refused.
If your project accepts coordinate systems from users, switch to integer SRIDs, which Django looks up directly in the EPSG database. When strings are unavoidable on older GDAL builds, check them against a fixed allow list before passing them on.
Also check the GDAL version on your servers and in your container images. Full protection needs GDAL 3.9 or later, and a new system check called gis.W001 will now warn you when an older library is installed.
Finally, watch your cache hit rate for a day after the upgrade. A brief drop is expected and is not a sign that something broke.
How to Upgrade
Move to the latest patch release for your line: 6.1.3, 6.0.10 or 5.2.19. With pip, raise the version pin in your requirements file, reinstall, run your test suite and redeploy.
- Run python manage.py check after upgrading to see if the gis.W001 warning appears.
- Search your code for SpatialReference, transform() and srs calls that receive strings.
- Rebuild Docker images so they pick up both the new Django and, where possible, a newer GDAL.
Projects still on older, unsupported Django versions receive no fixes and should plan a move to 5.2 LTS or newer. For more Python reading, see our guide on the best programming language to learn in 2026.
Conclusion
This batch of Django fixes is broad but mostly low risk, with the GeoJSON SSRF flaw as the one that deserves fast action. Upgrade to 6.1.3, 6.0.10 or 5.2.19, update GDAL to 3.9 or later, and move any untrusted coordinate system input to integer SRIDs.
Sources
See my articles more often when you search Google.
