Debian Codegraph @

docs/releases/5.2.15.txt

raw
1 ===========================
2 Django 5.2.15 release notes
3 ===========================
4
5 *June 3, 2026*
6
7 Django 5.2.15 fixes five security issues with severity "low" in 5.2.14.
8
9 CVE-2026-6873: Signed cookie salt namespace collision
10 =====================================================
11
12 :meth:`~django.http.HttpRequest.get_signed_cookie` derived the signing salt by
13 concatenating the cookie name (``key``) and ``salt`` arguments. When distinct
14 name and salt pairs produced the same concatenation, cookies could be accepted
15 in a context different from the one where they were signed.
16
17 Cookies are now signed with an unambiguous salt derivation. For backwards
18 compatibility, cookies signed by older Django versions are accepted until
19 Django 7.0. Projects affected by the above ambiguity should set
20 :setting:`SIGNED_COOKIE_LEGACY_SALT_FALLBACK` to ``False`` to reject older
21 cookies immediately.
22
23 This issue has severity "low" according to the :ref:`Django security policy
24 <severity-levels>`.
25
26 CVE-2026-7666: Potential unencrypted email transmission via ``STARTTLS`` in the SMTP backend
27 ============================================================================================
28
29 When using :setting:`EMAIL_USE_TLS`, a failed ``STARTTLS`` handshake could
30 leave a partially-initialized connection that would subsequently be reused for
31 sending email without encryption. This can occur with ``fail_silently=True``,
32 as used by :func:`~django.core.mail.send_mail` and
33 :class:`~django.middleware.common.BrokenLinkEmailsMiddleware`, among others.
34 Connections configured with :setting:`EMAIL_USE_SSL` are not affected.
35
36 This issue has severity "low" according to the :ref:`Django security policy
37 <severity-levels>`.
38
39 CVE-2026-8404: Potential exposure of private data via case-sensitive ``Cache-Control`` directives
40 =================================================================================================
41
42 :class:`~django.middleware.cache.UpdateCacheMiddleware` and
43 :func:`~django.views.decorators.cache.cache_page` incorrectly cached responses
44 marked with private ``Cache-Control`` directives when using mixed or uppercase
45 values (e.g. ``Private``).
46
47 The :func:`~django.views.decorators.cache.cache_control` decorator and
48 :func:`~django.utils.cache.patch_cache_control` function were not affected,
49 since they normalize directives to lowercase. This issue only affects responses
50 where ``Cache-Control`` is set manually.
51
52 This issue has severity "low" according to the :ref:`Django security policy
53 <severity-levels>`.
54
55 CVE-2026-35193: Potential exposure of private data via missing ``Vary: Authorization``
56 ======================================================================================
57
58 :class:`~django.middleware.cache.UpdateCacheMiddleware` and
59 :func:`~django.views.decorators.cache.cache_page` decorator allowed responses
60 to requests bearing an ``Authorization`` header (and without ``Cache-Control:
61 public``) to be cached. To conform with the existing mechanism for constructing
62 cache keys, responses to these requests will now :ref:`vary on
63 <using-vary-headers>` ``Authorization``.
64
65 This issue has severity "low" according to the :ref:`Django security policy
66 <severity-levels>`.
67
68 CVE-2026-48587: Potential exposure of private data via whitespace padding in ``Vary`` header
69 ============================================================================================
70
71 :class:`~django.middleware.cache.UpdateCacheMiddleware` incorrectly cached
72 responses whose ``Vary`` header values contained leading or trailing
73 whitespace. Because ``has_vary_header()`` failed to strip that, a ``Vary: *``
74 header value with surrounding whitespace was not recognized as containing the
75 wildcard, causing it to be stored and potentially served from the cache when it
76 should not have been.
77
78 This issue has severity "low" according to the :ref:`Django security policy
79 <severity-levels>`.