An issue was discovered in Django 6.0 before 6.0.7 and 5.2 before 5.2.16.
`DomainNameValidator` does not prohibit newlines in domain names (unless used via a form field, since `CharField` strips newlines). If an application uses values with newlines in an HTTP response, header injection can occur. Django itself is unaffected because `HttpResponse` prohibits newlines in HTTP headers.
Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank Bence Nagy for reporting this issue.
An issue was discovered in Django 6.0 before 6.0.7 and 5.2 before 5.2.16.
`django.contrib.gis.gdal.GDALRaster` over-reads its in-memory buffer when constructed from a bytes object, which can disclose adjacent memory or cause service degradation via a potential segmentation fault when the `vsi_buffer` property is accessed.
Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank Bence Nagy for reporting this issue.
An issue was discovered in Django 5.2 before 5.2.15 and 6.0 before 6.0.6. `django.middleware.cache.UpdateCacheMiddleware` in Django does not match `Cache-Control` response directives case-insensitively, which allows remote attackers to read responses that were incorrectly cached because their `Cache-Control` directives used uppercase or mixed-case values. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Ahmed Badawe for reporting this issue.
CVE-2026-6873 is a low-severity vulnerability in Django versions 6.0 and 5.2 where the get_signed_cookie function uses a non-injective salt derivation method. This flaw allows an attacker to reuse a signed cookie in a different context by exploiting distinct (name, salt) pairs that produce the same concatenation. The issue affects Django 6.0 before 6.0.6 and 5.2 before 5.2.15, with earlier unsupported versions possibly also affected. No official patch or remediation level has been confirmed yet.
An issue was discovered in Django 5.2 before 5.2.15 and 6.0 before 6.0.6.
`django.utils.cache.has_vary_header()` in Django does not strip leading or trailing whitespace from `Vary` response header values before comparison, which allows remote attackers to read cached responses via requests to URLs whose responses contain whitespace-padded Vary header values.
Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank Navid Rezazadeh for reporting this issue.
A vulnerability in Django's UpdateCacheMiddleware allows private cached responses to be read by unauthenticated remote attackers. This occurs because the middleware does not add the Authorization header to the Vary response header for requests that include Authorization without Cache-Control: public. The issue affects Django versions 5.2 before 5.2.15 and 6.0 before 6.0.6. Earlier unsupported versions may also be affected. The vulnerability has a low severity score and no known exploits in the wild.
A vulnerability in Django's SMTP email backend allows an on-path attacker to intercept email content in cleartext if a STARTTLS handshake fails and the connection is reused with fail_silently=True. This affects Django versions 6.0 and 5.2. The issue arises because the backend does not prevent reuse of a partially-initialized connection after a failed STARTTLS attempt. The severity is rated low with a CVSS score of 3.1.
Bence Nagy discovered that GeoDjango in Django incorrectly handled spatial
lookups when processing untrusted input. A remote attacker could possibly
use this issue to make outbound network requests, write arbitrary files, or
execute arbitrary code. This issue was only addressed in Ubuntu 22.04 LTS,
Ubuntu 24.04 LTS and Ubuntu 26.04 LTS. (CVE-2026-15307)
Ahmad Sadeddin discovered that Django UpdateCacheMiddleware incorrectly
cached requests where the Vary header contained an asterisk. A remote
attacker could possibly use this issue to obtain sensitive information.
(CVE-2026-6907)
Ahmed Badawe discovered that Django did not properly parse Cache-Control
response directives case-insensitively under certain circumstances. A
remote attacker could possibly use this issue to view sensitive information
from responses that were incorrectly cached. This issue only affected
Ubuntu 20.04 LTS, Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, and Ubuntu 26.04 LTS.
(CVE-2026-8404)
A vulnerability in Django versions 6.0 before 6.0.5 and 5.2 before 5.2.14 allows a remote attacker to steal a user's session if the user visits a cached public page and the SESSION_SAVE_EVERY_REQUEST setting is enabled. The issue arises because response headers do not vary on cookies when the session is unmodified, potentially exposing persistent cookies containing sensitive information. Earlier unsupported Django versions may also be affected. The CVSS score is low (2.
CVE-2026-5766 is a vulnerability in Django versions 6.0 before 6.0.5 and 5.2 before 5.2.14 where ASGI requests with a missing or understated Content-Length header can bypass the FILE_UPLOAD_MAX_MEMORY_SIZE limit. This can lead to large files being loaded into memory, potentially causing service degradation. The issue affects the handling of length parameters in file uploads. Django recommends configuring upload size limits at the web server level.
A vulnerability in Django versions 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30 allows ASGI requests with missing or understated Content-Length headers to bypass the DATA_UPLOAD_MAX_MEMORY_SIZE limit.
CVE-2026-33033 is a medium severity vulnerability in Django versions prior to 6.0.4, 5.2.13, and 4.2.30. It involves inefficient algorithmic complexity in the MultiPartParser component, where remote attackers can degrade server performance by submitting multipart uploads with 'Content-Transfer-Encoding: base64' containing excessive whitespace. This issue affects specific supported versions of Django and potentially earlier unsupported versions. No official patch or remediation guidance is currently confirmed.
CVE-2026-4292 is a low-severity vulnerability in Django versions prior to 6.0.4, 5.2.13, and 4.2.30. It involves missing authorization checks in admin changelist forms that use ModelAdmin.list_editable, allowing creation of new instances via forged POST data. Earlier unsupported Django versions may also be affected.
An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30.
Add permissions on inline model instances were not validated on submission of
forged `POST` data in `GenericInlineModelAdmin`.
Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank N05ec@LZU-DSLab for reporting this issue.
CVE-2026-3902 is an authentication bypass vulnerability in Django versions prior to 6.0.4, 5.2.13, and 4.2.30. It arises from ambiguous handling of HTTP headers in ASGIRequest, where headers with hyphens and underscores are mapped ambiguously, allowing remote attackers to spoof headers. This can lead to authentication bypass by spoofing. The vulnerability has a high severity with a CVSS score of 7.
An issue was discovered in 6.0 before 6.0.3, 5.2 before 5.2.12, and 4.2 before 4.2.29.
Race condition in file-system storage and file-based cache backends in Django allows an attacker to cause file system objects to be created with incorrect permissions via concurrent requests, where one thread's temporary `umask` change affects other threads in multi-threaded environments.
Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank Tarek Nakkouch for reporting this issue.
An issue was discovered in 6.0 before 6.0.3, 5.2 before 5.2.12, and 4.2 before 4.2.29.
`URLField.to_python()` in Django calls `urllib.parse.urlsplit()`, which performs NFKC normalization on Windows that is disproportionately slow for certain Unicode characters, allowing a remote attacker to cause denial of service via large URL inputs containing these characters.
Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank Seokchan Yoon for reporting this issue.
An issue was discovered in 6.0 before 6.0.2, 5.2 before 5.2.11, and 4.2 before 4.2.28.
`ASGIRequest` allows a remote attacker to cause a potential denial-of-service via a crafted request with multiple duplicate headers.
Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank Jiyong Yang for reporting this issue.
An issue was discovered in 6.0 before 6.0.2, 5.2 before 5.2.11, and 4.2 before 4.2.28.
`.QuerySet.order_by()` is subject to SQL injection in column aliases containing periods when the same alias is, using a suitably crafted dictionary, with dictionary expansion, used in `FilteredRelation`.
Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank Solomon Kebede for reporting this issue.
An issue was discovered in 6.0 before 6.0.2, 5.2 before 5.2.11, and 4.2 before 4.2.28.
`FilteredRelation` is subject to SQL injection in column aliases via control characters, using a suitably crafted dictionary, with dictionary expansion, as the `**kwargs` passed to `QuerySet` methods `annotate()`, `aggregate()`, `extra()`, `values()`, `values_list()`, and `alias()`.
Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank Solomon Kebede for reporting this issue.