Debian Codegraph @

docs/releases/5.2.14.txt

raw
1 ===========================
2 Django 5.2.14 release notes
3 ===========================
4
5 *May 5, 2026*
6
7 Django 5.2.14 fixes three security issues with severity "low" in 5.2.13.
8 Django 5.2.14 fixes three security issue with severity "low" in 5.2.13.
9
10 CVE-2026-5766: Potential denial-of-service vulnerability in ASGI requests via file upload limit bypass
11 ======================================================================================================
12
13 ASGI requests with a missing or understated ``Content-Length`` header could
14 bypass the :setting:`FILE_UPLOAD_MAX_MEMORY_SIZE` limit, potentially loading
15 large files into memory and causing service degradation.
16
17 As a reminder, Django :ref:`expects a limit to be configured
18 <user-uploaded-content-security>` at the web server level rather than solely
19 relying on :setting:`FILE_UPLOAD_MAX_MEMORY_SIZE`.
20
21 This issue has severity "low" according to the :ref:`Django security policy
22 <severity-levels>`.
23
24 CVE-2026-35192: Session fixation via public cached pages and ``SESSION_SAVE_EVERY_REQUEST``
25 ===========================================================================================
26
27 Response headers did not :ref:`vary on <using-vary-headers>` cookies if a
28 session was not modified, but :setting:`SESSION_SAVE_EVERY_REQUEST` was
29 ``True``. A remote attacker could steal a user's session after that user visits
30 a cached public page.
31
32 This issue has severity "low" according to the :ref:`Django security policy
33 <severity-levels>`.
34
35 CVE-2026-6907: Potential exposure of private data due to incorrect handling of ``Vary: *`` in ``UpdateCacheMiddleware``
36 =======================================================================================================================
37
38 Previously, :class:`~django.middleware.cache.UpdateCacheMiddleware` would
39 erroneously cache requests where the ``Vary`` header contained an asterisk
40 (``'*'``). This could lead to private data being stored and served.
41
42 This issue has severity "low" according to the :ref:`Django security policy
43 <severity-levels>`.