RepoJournal
Django

@django

Python's batteries-included web framework

Keep up with Django in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

One email a day. Unsubscribe in one click.

Pick a date

Topics: Python Full archive →

The Wire · Showcase

DJANGO PATCHES THREE CRITICAL CACHE AND UPLOAD VULNERABILITIES

By RepoJournal · Filed · About Django

Django shipped fixes overnight for three security flaws affecting cache headers, session handling, and ASGI file uploads that could let attackers bypass critical safety limits.

Three CVEs hit the archive simultaneously [1], each addressing a distinct attack surface. CVE-2026-6907 [2] fixes a cache poisoning vulnerability where requests with wildcard Vary headers were being cached when they shouldn't be — a bypass that could serve stale data to the wrong users. CVE-2026-35192 [3] ensures the Vary header is actually sent when SESSION_SAVE_EVERY_REQUEST=True, preventing session fixation attacks in certain configurations. The most dangerous is CVE-2026-5766 [4], which exploits ASGI deployments specifically: attackers could declare a small Content-Length header while uploading massive files, bypassing DATA_UPLOAD_MAX_MEMORY_SIZE entirely and crashing your workers. The ASGI vulnerability is critical if you're running Django on async servers — the fix enforces memory limits regardless of what the client claims to be sending.

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] Added CVE-2026-5766, CVE-2026-35192, and CVE-2026-6907 to security archive. django/django
  2. [2] Fixed CVE-2026-6907 -- Prevented caching of requests when Vary header contains an asterisk. django/django
  3. [3] Fixed CVE-2026-35192 -- Ensured Vary header is sent when setting session cookie with SESSION_SAVE_EVERY_REQUEST=True. django/django
  4. [4] Fixed CVE-2026-5766 -- Enforced DATA_UPLOAD_MAX_MEMORY_SIZE in MemoryFileUploadHandler on ASGI. django/django

Quick answers

What shipped in Django on May 6, 2026?
Django shipped fixes overnight for three security flaws affecting cache headers, session handling, and ASGI file uploads that could let attackers bypass critical safety limits. In total, 7 commits and 1 pull requests landed.
What were the notable Django updates?
Added CVE-2026-5766, CVE-2026-35192, and CVE-2026-6907 to security archive, Fixed CVE-2026-6907 -- Prevented caching of requests when Vary header contains an asterisk, and Fixed CVE-2026-35192 -- Ensured Vary header is sent when setting session cookie with SESSION_SAVE_EVERY_REQUEST=True.

More from @django

Daily updates, in your inbox

Follow Django

Keep up with Django in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

One email a day. Unsubscribe in one click. Read a past issue →

Elsewhere on the wire

Want every project, not just this one?