Django releases 6.0.7 and 5.2.16 to fix security issues
Django has released versions 6.0.7 and 5.2.16 to address three low-severity security issues across supported branches.
HEISE DEVELOPER — The fixes cover a cached Set-Cookie exposure risk, a heap buffer over-read in GDALRaster, and a header injection possibility in DomainNameValidator. Users are advised to upgrade promptly.
The Django team has released security updates 6.0.7 and 5.2.16 on July 7, 2026, to address three vulnerabilities classified as low severity. Patches have been applied to the main, 6.1 beta, 6.0, and 5.2 branches.
CVE-2026-48588 involves a flaw in UpdateCacheMiddleware and the cache_page decorator. When a request already contained an unrelated cookie, the system could inadvertently store responses containing sensitive session or Set-Cookie cookies in the shared cache, potentially exposing private data.
CVE-2026-53877 describes a heap buffer over-read in GDALRaster. When instantiated with a bytes object for a raster file in GDAL's virtual filesystem, the vsi_buffer property could read approximately 32 bytes beyond the allocated buffer, leading to potential memory disclosure or segmentation faults.
CVE-2026-53878 concerns DomainNameValidator, which permitted newlines in input. While Django's HttpResponse prevents header injection by prohibiting newlines, the validator's behavior could be exploited if used outside of standard Django form fields, which normally strip such characters.
Readers’ Forum
No contributions yet — open the debate.
Open the discussion
No account or password needed — just enter your e-mail and we’ll send you a one-time sign-in link. First time here? You’re set up automatically.
Your rating will be applied automatically after you sign in.
Check your inbox
We’ve sent a sign-in link to …. Open it on this device — this tab will sign you in automatically.
Waiting for your click …
·