Loading story…
Django maintainers released urgent security updates addressing six vulnerabilities affecting multiple supported branches, including three high-severity SQL injection flaws and multiple denial-of-service (DoS) vectors. The issues impact Django 4.2, 5.2, 6.0, and the main development branch, with fixed releases called out as Django 4.2.28, 5.2.11, and 6.0.2.
The most severe fixes cover SQL injection paths that can allow execution of arbitrary SQL: CVE-2026-1207 affects PostGIS users via raster lookups on GIS fields when untrusted input is used as a band index; CVE-2026-1287 involves FilteredRelation SQL injection through column aliases containing control characters when crafted dictionaries are expanded into QuerySet methods (e.g., annotate(), aggregate(), values()); and CVE-2026-1312 targets QuerySet.order_by() with FilteredRelation via column aliases containing periods. DoS fixes include CVE-2025-14550 (resource exhaustion via repeated/duplicate headers in ASGI deployments) and CVE-2026-1285 (DoS in django.utils.text.Truncator HTML methods), alongside a low-severity timing issue CVE-2025-13473 that can enable username enumeration in a mod_wsgi authentication handler.
See affected versions and whether adversaries are exploiting it.
2 events from the most recent confirmed update back to the earliest known activity.
Django published fixed releases 6.0.2, 5.2.11, and 4.2.28, along with GitHub changesets for affected branches. The advisory urged immediate upgrades, especially for deployments using PostGIS, ASGI servers, or FilteredRelation-based queries.
The Django development team issued urgent security updates addressing six flaws affecting Django 4.2, 5.2, 6.0, and the main development branch. The issues included three high-severity SQL injection vulnerabilities, multiple denial-of-service risks, and a low-severity username-enumeration timing issue in mod_wsgi authentication.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
The Django project released **Django 6.0.8** and **Django 5.2.17** to fix four vulnerabilities, led by **`CVE-2026-15307`**, a high-severity flaw in GeoDjango spatial lookups. The bug affects cases where untrusted `str` or `dict` input is passed to `django.contrib.gis.gdal.GDALRaster`, allowing attacker-controlled server-side file writes and outbound requests through GDAL virtual filesystem handlers; in some deployments, that file-write primitive can be chained into **remote code execution** if the written file is later imported by the application. Reports said the issue could be exploited remotely with low privileges, including by a staff user through a Django admin changelist query string. The same releases also addressed **`CVE-2026-15337`**, a low-severity denial-of-service issue in `check_for_language()`; **`CVE-2026-15830`**, a moderate denial-of-service flaw triggered by deeply nested `GEOMETRYCOLLECTION` objects in `GEOSGeometry`; and **`CVE-2026-15920`**, a moderate stored cross-site scripting issue in Django admin rendering of `URLField` values. Supported branches including Django main, the 6.1 release candidate, 6.0, and 5.2 received fixes, and the project urged users to upgrade promptly; older unsupported branches such as **5.1.x**, **5.0.x**, and **4.2.x** were not evaluated and may also be affected.
Aug 6, 2026
The Django development team released a security update addressing two critical vulnerabilities: a high-severity SQL injection flaw (CVE-2025-64459) and a denial-of-service (DoS) bug (CVE-2025-64458). The SQL injection vulnerability, present in Django's Object-Relational Mapper (ORM), could allow attackers to manipulate database queries and compromise data integrity if exploited. The DoS vulnerability could enable attackers to disrupt application availability by sending specially crafted requests. Security researchers highlighted that these flaws expose underlying risks in Django's ORM, which is widely trusted for its built-in security features. The incident underscores the importance of regular security reviews and prompt patching, even for mature frameworks. Organizations using Django are strongly advised to apply the latest security updates to mitigate these threats and reassess their reliance on default ORM protections.
Jun 29, 2026
The Django project issued a series of security releases across supported branches, publishing fixes for versions **6.0**, **5.2**, and **4.2**. The March advisory announced **Django 6.0.3**, **5.2.12**, and **4.2.29**, while a follow-up April advisory delivered **6.0.4**, **5.2.13**, and **4.2.30**. Release-note pages were also published for the affected branches, including **6.0.2**, **6.0.4**, **5.2.13**, **4.2.28**, and **4.2.30**, indicating ongoing maintenance and patching activity across the framework's supported versions. The updates show Django responding with successive security patches rather than a single one-off fix, with coordinated releases spanning current and long-term support branches. Organizations running Django applications should verify which branch they use and upgrade to the latest patched release in that series—**6.0.4**, **5.2.13**, or **4.2.30**—to ensure they have the most recent security corrections published by the project.
Jul 12, 2026