From 17b93fa0816e13878646200ca4e0c38871b52e78 Mon Sep 17 00:00:00 2001 From: Sarah Boyce <42296566+sarahboyce@users.noreply.github.com> Date: Tue, 5 May 2026 16:30:51 +0200 Subject: Added CVE-2026-5766, CVE-2026-35192, and CVE-2026-6907 to security archive. --- docs/releases/security.txt | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) (limited to 'docs') diff --git a/docs/releases/security.txt b/docs/releases/security.txt index b689d90f1d..fc79d72d25 100644 --- a/docs/releases/security.txt +++ b/docs/releases/security.txt @@ -36,6 +36,38 @@ Issues under Django's security process All security issues have been handled under versions of Django's security process. These are listed below. +May 5, 2026 - :cve:`2026-5766` +------------------------------ + +Potential denial-of-service vulnerability in ASGI requests via file upload +limit bypass. +`Full description +`__ + +* Django 6.0 :commit:`(patch) ` +* Django 5.2 :commit:`(patch) <2ec27eda3ba6c14f0856e6e3eb1df07c41fd95e6>` + +May 5, 2026 - :cve:`2026-35192` +------------------------------- + +Session fixation via public cached pages and ``SESSION_SAVE_EVERY_REQUEST``. +`Full description +`__ + +* Django 6.0 :commit:`(patch) <1b0184aa657bc3f5859aeb0206e7c1e94e48b103>` +* Django 5.2 :commit:`(patch) <47cf968c125e3fab317e10fe150ec479e745f995>` + +May 5, 2026 - :cve:`2026-6907` +------------------------------ + +Potential exposure of private data due to incorrect handling of ``Vary: *`` in +``UpdateCacheMiddleware``. +`Full description +`__ + +* Django 6.0 :commit:`(patch) <44ad76efcbe3c4ca0f08bb9dabe916f6374596c9>` +* Django 5.2 :commit:`(patch) <2115d4eaee15107f5cd290d7cfcc5ffe3ad43661>` + April 7, 2026 - :cve:`2026-3902` -------------------------------- -- cgit v1.3