Quick answers
- Is CVE-2026-114582 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-114582 being exploited in the wild.
- How severe is CVE-2026-114582?
- Medium severity, with a CVSS score of 5.3, published 3 November 2026.
- Which products and versions are affected?
- Django Software Foundation Django 6.1 before 6.1.3, 6.0 before 6.0.10, 5.2 before 5.2.19, and potentially 5.1.x, 5.0.x, 4.2.x.
- Is there a fix for CVE-2026-114582?
- Yes: fixed in Django 6.1.3, 6.0.10, 5.2.19. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-114582 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-114582?
- Check whether you run Django Software Foundation Django at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Django 6.1.3, 6.0.10, 5.2.19
Technical details
The vulnerability exists in django.contrib.gis.gdal.SpatialReference and related transform() methods and srs/srid setters, which do not restrict GDAL's file and network access when parsing string input. An attacker can craft malicious spatial reference strings to trigger server-side requests (SSRF) or local file reads (LFI). The vulnerability affects Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19, with potentially unsupported earlier versions also affected.
Affected products
- Django Software Foundation Django 6.1 before 6.1.3, 6.0 before 6.0.10, 5.2 before 5.2.19, and potentially 5.1.x, 5.0.x, 4.2.x
Timeline
- 2026-11-03: disclosed