| 1 |
=========================== |
| 2 |
Django 4.2.28 release notes |
| 3 |
=========================== |
| 4 |
|
| 5 |
*February 3, 2026* |
| 6 |
|
| 7 |
Django 4.2.28 fixes three security issues with severity "high", two security |
| 8 |
issues with severity "moderate", and one security issue with severity "low" in |
| 9 |
4.2.27. |
| 10 |
|
| 11 |
CVE-2025-13473: Username enumeration through timing difference in mod_wsgi authentication handler |
| 12 |
================================================================================================= |
| 13 |
|
| 14 |
The ``django.contrib.auth.handlers.modwsgi.check_password()`` function for |
| 15 |
:doc:`authentication via mod_wsgi</howto/deployment/wsgi/apache-auth>` |
| 16 |
allowed remote attackers to enumerate users via a timing attack. |
| 17 |
|
| 18 |
This issue has severity "low" according to the :ref:`Django security policy |
| 19 |
<severity-levels>`. |
| 20 |
|
| 21 |
CVE-2025-14550: Potential denial-of-service vulnerability via repeated headers when using ASGI |
| 22 |
============================================================================================== |
| 23 |
|
| 24 |
When receiving duplicates of a single header, ``ASGIRequest`` allowed a remote |
| 25 |
attacker to cause a potential denial-of-service via a specifically created |
| 26 |
request with multiple duplicate headers. The vulnerability resulted from |
| 27 |
repeated string concatenation while combining repeated headers, which |
| 28 |
produced super-linear computation resulting in service degradation or outage. |
| 29 |
|
| 30 |
This issue has severity "moderate" according to the :ref:`Django security |
| 31 |
policy <severity-levels>`. |
| 32 |
|
| 33 |
CVE-2026-1207: Potential SQL injection via raster lookups on PostGIS |
| 34 |
==================================================================== |
| 35 |
|
| 36 |
:ref:`Raster lookups <spatial-lookup-raster>` on GIS fields (only implemented |
| 37 |
on PostGIS) were subject to SQL injection if untrusted data was used as a band |
| 38 |
index. |
| 39 |
|
| 40 |
As a reminder, all untrusted user input should be validated before use. |
| 41 |
|
| 42 |
This issue has severity "high" according to the :ref:`Django security policy |
| 43 |
<severity-levels>`. |
| 44 |
|
| 45 |
CVE-2026-1285: Potential denial-of-service vulnerability in ``django.utils.text.Truncator`` HTML methods |
| 46 |
======================================================================================================== |
| 47 |
|
| 48 |
``django.utils.text.Truncator.chars()`` and ``Truncator.words()`` methods (with |
| 49 |
``html=True``) and the :tfilter:`truncatechars_html` and |
| 50 |
:tfilter:`truncatewords_html` template filters were subject to a potential |
| 51 |
denial-of-service attack via certain inputs with a large number of unmatched |
| 52 |
HTML end tags, which could cause quadratic time complexity during HTML parsing. |
| 53 |
|
| 54 |
This issue has severity "moderate" according to the :ref:`Django security |
| 55 |
policy <severity-levels>`. |
| 56 |
|
| 57 |
CVE-2026-1287: Potential SQL injection in column aliases via control characters |
| 58 |
=============================================================================== |
| 59 |
|
| 60 |
:class:`.FilteredRelation` was subject to SQL injection in column aliases via |
| 61 |
control characters, using a suitably crafted dictionary, with dictionary |
| 62 |
expansion, as the ``**kwargs`` passed to :meth:`.QuerySet.annotate`, |
| 63 |
:meth:`~.QuerySet.aggregate`, :meth:`~.QuerySet.extra`, |
| 64 |
:meth:`~.QuerySet.values`, :meth:`~.QuerySet.values_list`, and |
| 65 |
:meth:`~.QuerySet.alias`. |
| 66 |
|
| 67 |
This issue has severity "high" according to the :ref:`Django security policy |
| 68 |
<severity-levels>`. |
| 69 |
|
| 70 |
CVE-2026-1312: Potential SQL injection via ``QuerySet.order_by`` and ``FilteredRelation`` |
| 71 |
========================================================================================= |
| 72 |
|
| 73 |
:meth:`.QuerySet.order_by` was subject to SQL injection in column aliases |
| 74 |
containing periods when the same alias was, using a suitably crafted |
| 75 |
dictionary, with dictionary expansion, used in :class:`.FilteredRelation`. |
| 76 |
|
| 77 |
This issue has severity "high" according to the :ref:`Django security policy |
| 78 |
<severity-levels>`. |