April 7, 2026
Django 5.2.13 fixes one security issue with severity "moderate" and four security issues with severity "low" in 5.2.12.
ASGIRequest normalizes header names following WSGI conventions, mapping
hyphens to underscores. As a result, even in configurations where reverse
proxies carefully strip security-sensitive headers named with hyphens, such a
header could be spoofed by supplying a header named with underscores.
Under WSGI, it is the responsibility of the server or proxy to avoid ambiguous
mappings. (Django's runserver was patched in CVE 2015-0219.) But
under ASGI, there is not the same uniform expectation, even if many proxies
protect against this under default configuration (including nginx via
underscores_in_headers off;).
Headers containing underscores are now ignored by ASGIRequest, matching the
behavior of Daphne, the reference server for ASGI.
根据 Django 安全政策,这个问题的严重性为“低”。
GenericInlineModelAdmin¶Add permissions on inline model instances were not validated on submission of
forged POST data in
GenericInlineModelAdmin.
根据 Django 安全政策,这个问题的严重性为“低”。
ModelAdmin.list_editable¶Admin changelist forms using
list_editable incorrectly allowed new
instances to be created via forged POST data.
根据 Django 安全政策,这个问题的严重性为“低”。
MultiPartParser via base64-encoded file upload¶When using django.http.multipartparser.MultiPartParser, multipart uploads
with Content-Transfer-Encoding: base64 that include excessive whitespace
may trigger repeated memory copying, potentially degrading performance.
This issue has severity "moderate" according to the Django security policy.
ASGI requests with a missing or understated Content-Length header could
bypass the DATA_UPLOAD_MAX_MEMORY_SIZE limit when reading
HttpRequest.body, potentially loading an unbounded request body into
memory and causing service degradation.
根据 Django 安全政策,这个问题的严重性为“低”。
4月 20, 2026
本文整理自 Django 6.0 官方中文文档,转载请注明出处。
上一篇:Django 5.2.12 release notes — Django 6.0.4 documentation(2026)
下一篇:Django 5.2.13 release notes — Django 6.0.4 documentation(2026)