unstale

pypi / django

django

What changed in django 5 to 6, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-21.

30 security

See which of these apply to your code, ranked, in your agent:

npx @unstale/cli init

@unstale/cli 0.2.2 on npm

django 626 changes

Security 26

  • Django GeoDjango vulnerable to denial of service through deeply nested geometry collections

    5.2.17, 6.0.8, 6.1.1security advisory

  • Django GeoDjango spatial lookups allow file writes and outbound requests through GDAL raster parsing

    5.2.17, 6.0.8security advisory

  • Django: cache middleware may expose private responses when unrelated request cookies are present

    5.2.16, 6.0.7security advisory

  • Django: DomainNameValidator permits newline characters that may enable HTTP header injection

    5.2.16, 6.0.7security advisory

  • Django: GDALRaster may over-read heap memory when constructed from bytes

    5.2.16, 6.0.7security advisory

  • Django fails to prevent reuse of a partially-initialized connection after a failed STARTTLS handshake

    5.2.15, 6.0.6security advisory

  • Django: has_vary_header may expose cached responses when Vary values contain whitespace

    5.2.15, 6.0.6security advisory

  • Django: signed cookies are vulnerable to salt namespace collisions

    5.2.15, 6.0.6security advisory

  • Django: UpdateCacheMiddleware may disclose cached responses due to case-sensitive Cache-Control handling

    5.2.15, 6.0.6security advisory

  • Django: UpdateCacheMiddleware may disclose private cached responses by omitting Authorization from Vary

    5.2.15, 6.0.6security advisory

  • Django has an Improper Handling of Length Parameter Inconsistency

    5.2.14, 6.0.5security advisory

  • Django Uses Cache Containing Sensitive Information

    5.2.14, 6.0.5security advisory

  • Django Uses Persistent Cookies Containing Sensitive Information

    5.2.14, 6.0.5security advisory

  • Django has potential DoS via MultiPartParser through crafted multipart uploads

    4.2.30, 5.2.13, 6.0.4security advisory

  • Django: SGI requests with a missing or understated Content-Length header could bypass the DATA_UPLOAD_MAX_MEMORY_SIZE limit

    4.2.30, 5.2.13, 6.0.4security advisory

  • Django vulnerable to ASGI header spoofing via underscore/hyphen conflation

    4.2.30, 5.2.13, 6.0.4security advisory

  • Django vulnerable to privilege abuse in GenericInlineModelAdmin

    4.2.30, 5.2.13, 6.0.4security advisory

  • Django vulnerable to privilege abuse in ModelAdmin.list_editable

    4.2.30, 5.2.13, 6.0.4security advisory

  • Django has a Race Condition vulnerability

    4.2.29, 5.2.12, 6.0.3security advisory

  • Django vulnerable to Uncontrolled Resource Consumption

    4.2.29, 5.2.12, 6.0.3security advisory

  • Django has an SQL Injection issue

    4.2.28, 5.2.11, 6.0.2security advisory

  • Django has an SQL Injection issue

    4.2.28, 5.2.11, 6.0.2security advisory

  • Django has an SQL Injection issue

    4.2.28, 5.2.11, 6.0.2security advisory

  • Django has Inefficient Algorithmic Complexity

    4.2.28, 5.2.11, 6.0.2security advisory

  • Django has Inefficient Algorithmic Complexity

    4.2.28, 5.2.11, 6.0.2security advisory

  • Django has Observable Timing Discrepancy

    4.2.28, 5.2.11, 6.0.2security advisory

django 54 changes

Security 4

  • Django is vulnerable to DoS via XML serializer text extraction

    4.2.27, 5.1.15, 5.2.9security advisory

  • Django is vulnerable to SQL injection in column aliases

    4.2.27, 5.1.15, 5.2.9security advisory

  • Django has a denial-of-service vulnerability in HttpResponseRedirect and HttpResponsePermanentRedirect on Windows

    4.2.26, 5.1.14, 5.2.8security advisory

  • Django vulnerable to SQL injection via _connector keyword argument in QuerySet and Q objects.

    4.2.26, 5.1.14, 5.2.8security advisory