CVE-2026-33033

An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. MultiPartParser allows remote attackers to degrade performance by submitting multipart uploads with Content-Transfer-Encoding: base64 including excessive whitespace. 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.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. MultiPartParser allows remote attackers to degrade performance by submitting multipart uploads with Content-Transfer-Encoding: base64 including excessive whitespace.

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.

A high-level Python Web framework that encourages rapid development and clean, pragmatic design.

Security Fix(es):

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.(CVE-2026-25674)

An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. MultiPartParser allows remote attackers to degrade performance by submitting multipart uploads with Content-Transfer-Encoding: base64 including excessive whitespace. 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.(CVE-2026-33033)

An issue was discovered in Django's GenericInlineModelAdmin component. Add permissions on inline model instances were not validated on submission of forged POST data. This vulnerability affects Django 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. 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-4277)

An issue was discovered in Django 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Admin changelist forms using ModelAdmin.list_editable incorrectly allowed new instances to be created via forged POST data. 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 Cantina for reporting this issue.(CVE-2026-4292)

A high-level Python Web framework that encourages rapid development and clean, pragmatic design.

Security Fix(es):

An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. MultiPartParser allows remote attackers to degrade performance by submitting multipart uploads with Content-Transfer-Encoding: base64 including excessive whitespace. 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.(CVE-2026-33033)

An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. ASGI requests with a missing or understated Content-Length header could bypass the DATA_UPLOAD_MAX_MEMORY_SIZE limit when reading HttpRequest.body, allowing remote attackers to load an unbounded request body into memory. 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 Superior for reporting this issue.(CVE-2026-33034)

This issue was discovered in version 6.0, before 6.0.5, and before 5.2.14. If the session has not been modified, the cookie's response header does not change, but "SESSION_SAVE_EVERY_REQUEST" is "true". A remote attacker could steal a user's session after the user visits a cached public page. Earlier unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) have not been evaluated and may also be affected. Django thanks Cantina for reporting this issue.(CVE-2026-35192)

An issue was discovered in Django versions 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. ASGIRequest allows a remote attacker to spoof headers by exploiting an ambiguous mapping of two header variants (with hyphens or with underscores) to a single version with underscores. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.(CVE-2026-3902)

An issue was discovered in Django's GenericInlineModelAdmin component. Add permissions on inline model instances were not validated on submission of forged POST data. This vulnerability affects Django 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. 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-4277)

An issue was discovered in Django 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Admin changelist forms using ModelAdmin.list_editable incorrectly allowed new instances to be created via forged POST data. 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 Cantina for reporting this issue.(CVE-2026-4292)

When processing ASGI requests, if the Content-Length request header is deliberately omitted in a malicious request, or a false value is provided that is much smaller than the actual file, the system will be deceived, thereby bypassing Django's built-in FILE_UPLOAD_MAX_MEMORY_SIZE (maximum memory file upload limit)(CVE-2026-5766)

处理 ASGI 请求时，如果请求中缺少 Content-Length 请求头，或者人为提供了偏小的数值，就能绕过 Django 内置的 FILE_UPLOAD_MAX_MEMORY_SIZE（最大内存文件上传大小）限制(CVE-2026-6907)

A high-level Python Web framework that encourages rapid development and clean, pragmatic design.

Security Fix(es):

An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. MultiPartParser allows remote attackers to degrade performance by submitting multipart uploads with Content-Transfer-Encoding: base64 including excessive whitespace. 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.(CVE-2026-33033)

An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. ASGI requests with a missing or understated Content-Length header could bypass the DATA_UPLOAD_MAX_MEMORY_SIZE limit when reading HttpRequest.body, allowing remote attackers to load an unbounded request body into memory. 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 Superior for reporting this issue.(CVE-2026-33034)

This issue was discovered in version 6.0, before 6.0.5, and before 5.2.14. If the session has not been modified, the cookie's response header does not change, but "SESSION_SAVE_EVERY_REQUEST" is "true". A remote attacker could steal a user's session after the user visits a cached public page. Earlier unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) have not been evaluated and may also be affected. Django thanks Cantina for reporting this issue.(CVE-2026-35192)

An issue was discovered in Django versions 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. ASGIRequest allows a remote attacker to spoof headers by exploiting an ambiguous mapping of two header variants (with hyphens or with underscores) to a single version with underscores. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.(CVE-2026-3902)

An issue was discovered in Django's GenericInlineModelAdmin component. Add permissions on inline model instances were not validated on submission of forged POST data. This vulnerability affects Django 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. 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-4277)

An issue was discovered in Django 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Admin changelist forms using ModelAdmin.list_editable incorrectly allowed new instances to be created via forged POST data. 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 Cantina for reporting this issue.(CVE-2026-4292)

When processing ASGI requests, if the Content-Length request header is deliberately omitted in a malicious request, or a false value is provided that is much smaller than the actual file, the system will be deceived, thereby bypassing Django's built-in FILE_UPLOAD_MAX_MEMORY_SIZE (maximum memory file upload limit)(CVE-2026-5766)

处理 ASGI 请求时，如果请求中缺少 Content-Length 请求头，或者人为提供了偏小的数值，就能绕过 Django 内置的 FILE_UPLOAD_MAX_MEMORY_SIZE（最大内存文件上传大小）限制(CVE-2026-6907)

A high-level Python Web framework that encourages rapid development and clean, pragmatic design.

Security Fix(es):

An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. MultiPartParser allows remote attackers to degrade performance by submitting multipart uploads with Content-Transfer-Encoding: base64 including excessive whitespace. 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.(CVE-2026-33033)

An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. ASGI requests with a missing or understated Content-Length header could bypass the DATA_UPLOAD_MAX_MEMORY_SIZE limit when reading HttpRequest.body, allowing remote attackers to load an unbounded request body into memory. 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 Superior for reporting this issue.(CVE-2026-33034)

This issue was discovered in version 6.0, before 6.0.5, and before 5.2.14. If the session has not been modified, the cookie's response header does not change, but "SESSION_SAVE_EVERY_REQUEST" is "true". A remote attacker could steal a user's session after the user visits a cached public page. Earlier unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) have not been evaluated and may also be affected. Django thanks Cantina for reporting this issue.(CVE-2026-35192)

An issue was discovered in Django versions 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. ASGIRequest allows a remote attacker to spoof headers by exploiting an ambiguous mapping of two header variants (with hyphens or with underscores) to a single version with underscores. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.(CVE-2026-3902)

An issue was discovered in Django's GenericInlineModelAdmin component. Add permissions on inline model instances were not validated on submission of forged POST data. This vulnerability affects Django 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. 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-4277)

An issue was discovered in Django 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Admin changelist forms using ModelAdmin.list_editable incorrectly allowed new instances to be created via forged POST data. 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 Cantina for reporting this issue.(CVE-2026-4292)

When processing ASGI requests, if the Content-Length request header is deliberately omitted in a malicious request, or a false value is provided that is much smaller than the actual file, the system will be deceived, thereby bypassing Django's built-in FILE_UPLOAD_MAX_MEMORY_SIZE (maximum memory file upload limit)(CVE-2026-5766)

处理 ASGI 请求时，如果请求中缺少 Content-Length 请求头，或者人为提供了偏小的数值，就能绕过 Django 内置的 FILE_UPLOAD_MAX_MEMORY_SIZE（最大内存文件上传大小）限制(CVE-2026-6907)

A high-level Python Web framework that encourages rapid development and clean, pragmatic design.

Security Fix(es):

An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. MultiPartParser allows remote attackers to degrade performance by submitting multipart uploads with Content-Transfer-Encoding: base64 including excessive whitespace. 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.(CVE-2026-33033)

An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. ASGI requests with a missing or understated Content-Length header could bypass the DATA_UPLOAD_MAX_MEMORY_SIZE limit when reading HttpRequest.body, allowing remote attackers to load an unbounded request body into memory. 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 Superior for reporting this issue.(CVE-2026-33034)

This issue was discovered in version 6.0, before 6.0.5, and before 5.2.14. If the session has not been modified, the cookie's response header does not change, but "SESSION_SAVE_EVERY_REQUEST" is "true". A remote attacker could steal a user's session after the user visits a cached public page. Earlier unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) have not been evaluated and may also be affected. Django thanks Cantina for reporting this issue.(CVE-2026-35192)

An issue was discovered in Django versions 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. ASGIRequest allows a remote attacker to spoof headers by exploiting an ambiguous mapping of two header variants (with hyphens or with underscores) to a single version with underscores. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.(CVE-2026-3902)

An issue was discovered in Django's GenericInlineModelAdmin component. Add permissions on inline model instances were not validated on submission of forged POST data. This vulnerability affects Django 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. 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-4277)

An issue was discovered in Django 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Admin changelist forms using ModelAdmin.list_editable incorrectly allowed new instances to be created via forged POST data. 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 Cantina for reporting this issue.(CVE-2026-4292)

When processing ASGI requests, if the Content-Length request header is deliberately omitted in a malicious request, or a false value is provided that is much smaller than the actual file, the system will be deceived, thereby bypassing Django's built-in FILE_UPLOAD_MAX_MEMORY_SIZE (maximum memory file upload limit)(CVE-2026-5766)

处理 ASGI 请求时，如果请求中缺少 Content-Length 请求头，或者人为提供了偏小的数值，就能绕过 Django 内置的 FILE_UPLOAD_MAX_MEMORY_SIZE（最大内存文件上传大小）限制(CVE-2026-6907)

An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. MultiPartParser allows remote attackers to degrade performance by submitting multipart uploads with Content-Transfer-Encoding: base64 including excessive whitespace. 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.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. MultiPartParser allows remote attackers to degrade performance by submitting multipart uploads with Content-Transfer-Encoding: base64 including excessive whitespace. 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.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. MultiPartParser allows remote attackers to degrade performance by submitting multipart uploads with Content-Transfer-Encoding: base64 including excessive whitespace. 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.

TuxCare rebuilt django to address 1 CVE. Fixed in 4.2.post5+tuxcare.

TuxCare rebuilt django to address 7 CVEs. Fixed in 5.1.10.post8+tuxcare.

TuxCare rebuilt django to address 6 CVEs. Fixed in 4.0.post26+tuxcare.

TuxCare rebuilt django to address 7 CVEs. Fixed in 5.1.9.post10+tuxcare.

TuxCare rebuilt django to address 9 CVEs. Fixed in 3.2.25.post14+tuxcare.

TuxCare rebuilt django to address 4 CVEs. Fixed in 5.1.4.post11+tuxcare.

ASGI header spoofing via underscore/hyphen conflation. (CVE-2026-3902) Privilege abuse in GenericInlineModelAdmin. (CVE-2026-4277) Privilege abuse in ModelAdmin.list_editable. (CVE-2026-4292) Potential denial-of-service vulnerability in MultiPartParser via base64-encoded file upload. (CVE-2026-33033) Potential denial-of-service vulnerability in ASGI requests via memory upload limit bypass. (CVE-2026-33034)

These are all security issues fixed in the python311-Django4-4.2.30-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the python313-Django6-6.0.4-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the python311-Django-5.2.13-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the python313-Django5-5.2.16-1.1 package on the GA media of openSUSE Tumbleweed.

This update for python-Django fixes the following issues:

Changes in python-Django:

• CVE-2026-3902: ASGI header spoofing via underscore/hyphen conflation (bsc#1261729)
• CVE-2026-4277: Privilege abuse in GenericInlineModelAdmin (bsc#1261731)
• CVE-2026-4292: Privilege abuse in ModelAdmin.list_editable (bsc#1261732)
• CVE-2026-33033: Potential denial-of-service vulnerability in MultiPartParser via base64-encoded file upload (bsc#1261722)
• CVE-2026-33034: Potential denial-of-service vulnerability in ASGI requests via memory upload limit bypass (bsc#1261724)

This update for python-Django fixes the following issues

• CVE-2026-3902: headers spoofing by exploiting an ambiguous mapping of two header variants in ASGIRequest requests (bsc#1261729).
• CVE-2026-4277: permissions on inline model instances were not validated on submission of forged POST data in GenericInlineModelAdmin (bsc#1261731).
• CVE-2026-4292: admin changelist forms using ModelAdmin.list_editable incorrectly allowed new instances to be created via forged POST data (bsc#1261732).
• CVE-2026-5766: potential denial-of-service vulnerability in ASGI requests via file upload limit bypass (bsc#1264153).
• CVE-2026-6907: potential exposure of private data due to incorrect handling of Vary: * in UpdateCacheMiddleware (bsc#1264152).
• CVE-2026-33033: denial of service via missing or understated Content-Length header in ASGI requests (bsc#1261722).
• CVE-2026-33034: ASGI requests with a missing or understated Content-Length header could bypass the DATA_UPLOAD_MAX_MEMORY_SIZE limit when reading HttpRequest.body (bsc#1261724).
• CVE-2026-35192: session fixation via public cached pages and SESSION_SAVE_EVERY_REQUEST (bsc#1264154).

Seokchan Yoon discovered that Django incorrectly handled copying memory when parsing multipart uploads with excessive whitespace. A remote attacker could possibly use this issue to cause Django to use excessive resources, leading to a denial of service. (CVE-2026-33033)

It was discovered that Django did not enforce an upload memory size limit in the Content-Length header. A remote attacker could possibly use this issue to cause Django to use excessive resources, leading to a denial of service. This issue only affected Ubuntu 24.04 LTS and Ubuntu 25.10. (CVE-2026-33034)

Tarek Nakkouch discovered that Django incorrectly handled underscores in the ASGI headers. A remote attacker could possibly use this issue to spoof HTTP headers. This issue only affected Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, and Ubuntu 25.10. (CVE-2026-3902)

It was discovered that Django incorrectly handled verification of model data created with POST requests. A remote attacker could possibly use this issue to forge new model permissions. (CVE-2026-4277, CVE-2026-4292)

USN-8154-1 fixed vulnerabilities in Django. This update provides the corresponding updates for CVE-2026-33033 and CVE-2026-4292 in Ubuntu 14.04 LTS and Ubuntu 16.04 LTS, and CVE-2026-4277 in Ubuntu 16.04 LTS.

Original advisory details:

Seokchan Yoon discovered that Django incorrectly handled copying memory when parsing multipart uploads with excessive whitespace. A remote attacker could possibly use this issue to cause Django to use excessive resources, leading to a denial of service. (CVE-2026-33033)

It was discovered that Django did not enforce an upload memory size limit in the Content-Length header. A remote attacker could possibly use this issue to cause Django to use excessive resources, leading to a denial of service. This issue only affected Ubuntu 24.04 LTS and Ubuntu 25.10. (CVE-2026-33034)

Tarek Nakkouch discovered that Django incorrectly handled underscores in the ASGI headers. A remote attacker could possibly use this issue to spoof HTTP headers. This issue only affected Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, and Ubuntu 25.10. (CVE-2026-3902)

It was discovered that Django incorrectly handled verification of model data created with POST requests. A remote attacker could possibly use this issue to forge new model permissions. (CVE-2026-4277, CVE-2026-4292)