From: Peter Korsgaard <peter@korsgaard.com>
To: Marcus Hoffmann via buildroot <buildroot@buildroot.org>
Cc: Marcus Hoffmann <buildroot@bubu1.eu>,
James Hilliard <james.hilliard1@gmail.com>,
Manuel Diener <manuel.diener@oss.othermo.de>,
Oli Vogt <oli.vogt.pub01@gmail.com>,
Marcus Hoffmann <bubu@bubu1.eu>
Subject: Re: [Buildroot] [PATCH] package/python-django: security bump to 6.0.5
Date: Wed, 06 May 2026 19:21:07 +0200 [thread overview]
Message-ID: <873404qwsc.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20260506121800.507252-1-buildroot@bubu1.eu> (Marcus Hoffmann via buildroot's message of "Wed, 6 May 2026 14:17:58 +0200")
>>>>> "Marcus" == Marcus Hoffmann via buildroot <buildroot@buildroot.org> writes:
> Django 6.0.5 fixes three security issues with severity “low” and several bugs in 6.0.4.
> Security Fixes:
> * CVE-2026-5766: Potential denial-of-service vulnerability in ASGI
> requests via file upload limit bypass ASGI requests with a missing
> or understated Content-Length header could bypass the
> FILE_UPLOAD_MAX_MEMORY_SIZE limit, potentially loading large files into
> memory and causing service degradation.
> As a reminder, Django expects a limit to be configured at the web server
> level rather than solely relying on FILE_UPLOAD_MAX_MEMORY_SIZE.
> This issue has severity “low” according to the Django security policy
> * CVE-2026-35192: Session fixation via public cached pages and SESSION_SAVE_EVERY_REQUEST
> Response headers did not vary on cookies if a session was not modified,
> but SESSION_SAVE_EVERY_REQUEST was True. A remote attacker could steal a
> user’s session after that user visits a cached public page.
> This issue has severity “low” according to the Django security policy.
> * CVE-2026-6907: Potential exposure of private data due to incorrect
> handling of Vary: * in UpdateCacheMiddleware
> Previously, UpdateCacheMiddleware would erroneously cache requests where
> the Vary header contained an asterisk ('*'). This could lead to private
> data being stored and served.
> This issue has severity “low” according to the Django security policy.
> Bugfixes:
> * Fixed a misplaced </div> in the
> django/contrib/admin/templates/admin/change_list.html template added
> in Django 6.0 that could be problematic when overriding the pagination
> block (#37029).
> * Fixed a bug in Django 6.0 where deprecation warnings incorrectly
> skipped lines from third-party packages prefixed with “django”
> (#37067).
> Release notes: https://docs.djangoproject.com/en/6.0/releases/6.0.5/
> Signed-off-by: Marcus Hoffmann <buildroot@bubu1.eu>
Committed, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-05-06 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 12:17 [Buildroot] [PATCH] package/python-django: security bump to 6.0.5 Marcus Hoffmann via buildroot
2026-05-06 17:21 ` Peter Korsgaard [this message]
2026-05-15 17:45 ` Thomas Perale via buildroot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=873404qwsc.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=bubu@bubu1.eu \
--cc=buildroot@bubu1.eu \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=manuel.diener@oss.othermo.de \
--cc=oli.vogt.pub01@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox