| 1 |
=========================== |
| 2 |
Django 4.2.30 release notes |
| 3 |
=========================== |
| 4 |
|
| 5 |
*April 7, 2026* |
| 6 |
|
| 7 |
Django 4.2.30 fixes one security issue with severity "moderate" and four |
| 8 |
security issues with severity "low" in 4.2.29. |
| 9 |
|
| 10 |
CVE-2026-3902: ASGI header spoofing via underscore/hyphen conflation |
| 11 |
==================================================================== |
| 12 |
|
| 13 |
``ASGIRequest`` normalizes header names following WSGI conventions, mapping |
| 14 |
hyphens to underscores. As a result, even in configurations where reverse |
| 15 |
proxies carefully strip security-sensitive headers named with hyphens, such a |
| 16 |
header could be spoofed by supplying a header named with underscores. |
| 17 |
|
| 18 |
Under WSGI, it is the responsibility of the server or proxy to avoid ambiguous |
| 19 |
mappings. (Django's :djadmin:`runserver` was patched in :cve:`2015-0219`.) But |
| 20 |
under ASGI, there is not the same uniform expectation, even if many proxies |
| 21 |
protect against this under default configuration (including ``nginx`` via |
| 22 |
``underscores_in_headers off;``). |
| 23 |
|
| 24 |
Headers containing underscores are now ignored by ``ASGIRequest``, matching the |
| 25 |
behavior of :pypi:`Daphne <daphne>`, the reference server for ASGI. |
| 26 |
|
| 27 |
This issue has severity "low" according to the :ref:`Django security policy |
| 28 |
<severity-levels>`. |
| 29 |
|
| 30 |
CVE-2026-4277: Privilege abuse in ``GenericInlineModelAdmin`` |
| 31 |
============================================================= |
| 32 |
|
| 33 |
Add permissions on inline model instances were not validated on submission of |
| 34 |
forged ``POST`` data in |
| 35 |
:class:`~django.contrib.contenttypes.admin.GenericInlineModelAdmin`. |
| 36 |
|
| 37 |
This issue has severity "low" according to the :ref:`Django security policy |
| 38 |
<severity-levels>`. |
| 39 |
|
| 40 |
CVE-2026-4292: Privilege abuse in ``ModelAdmin.list_editable`` |
| 41 |
============================================================== |
| 42 |
|
| 43 |
Admin changelist forms using |
| 44 |
:attr:`~django.contrib.admin.ModelAdmin.list_editable` incorrectly allowed new |
| 45 |
instances to be created via forged ``POST`` data. |
| 46 |
|
| 47 |
This issue has severity "low" according to the :ref:`Django security policy |
| 48 |
<severity-levels>`. |
| 49 |
|
| 50 |
CVE-2026-33033: Potential denial-of-service vulnerability in ``MultiPartParser`` via base64-encoded file upload |
| 51 |
=============================================================================================================== |
| 52 |
|
| 53 |
When using ``django.http.multipartparser.MultiPartParser``, multipart uploads |
| 54 |
with ``Content-Transfer-Encoding: base64`` that include excessive whitespace |
| 55 |
may trigger repeated memory copying, potentially degrading performance. |
| 56 |
|
| 57 |
This issue has severity "moderate" according to the :ref:`Django security |
| 58 |
policy <severity-levels>`. |
| 59 |
|
| 60 |
CVE-2026-33034: Potential denial-of-service vulnerability in ASGI requests via memory upload limit bypass |
| 61 |
========================================================================================================= |
| 62 |
|
| 63 |
ASGI requests with a missing or understated ``Content-Length`` header could |
| 64 |
bypass the :setting:`DATA_UPLOAD_MAX_MEMORY_SIZE` limit when reading |
| 65 |
``HttpRequest.body``, potentially loading an unbounded request body into |
| 66 |
memory and causing service degradation. |
| 67 |
|
| 68 |
This issue has severity "low" according to the :ref:`Django security policy |
| 69 |
<severity-levels>`. |