StackPrism

PyPI package

Django 5.1.11 vulnerabilities, and the version that fixes all of them

Django 5.1.11 has 15 known vulnerabilities (5 rated high or critical); 5.2.17 fixes all of them. Django 5.1 reached end of life on Dec 3, 2025 and gets no more security fixes. Move to Django 5.2 (LTS).

PyPI (opens in a new tab) describes it as “A high-level Python web framework that encourages rapid development and clean, pragmatic design.”

Known vulnerabilities
15
5 rated high or critical
Released
Jun 10, 2025
Latest is 6.1.2
Django 5.1 support
End of life
Since Dec 3, 2025
Licence
BSD-3-Clause
OpenSSF Scorecard
6.7/10
django/django (opens in a new tab)
Pulls in
2 packages
Resolved by deps.dev

What to upgrade to

5.2.17 is the closest release with no known vulnerabilities.

  • 5.2.17Upgrade to this

    Fixes all 15 known vulnerabilities. Released Aug 4, 2026.

    No known vulnerabilities

  • 5.2.18

    Newest 5.x release. Released Oct 6, 2026.

    No known vulnerabilities

  • 6.1.2

    Latest release. Released Oct 6, 2026.

    No known vulnerabilities

5.2.17 came out on Aug 4, 2026. A coding agent trained before then doesn’t know it exists, so it may suggest an older release. AI knowledge cutoff dates

Hand the fix to your coding agent

One task with the upgrade, the file to change and why. Paste it into Claude Code, Cursor or Codex.

Findings

Every advisory for Django 5.1.11

Known exploited first (CISA KEV), then by how likely they are to be exploited (FIRST EPSS), then by severity. Each id links to its OSV.dev record.

  1. CriticalCVE-2025-57833 on OSV.dev (opens in a new tab)GHSA-6w2r-r2m5-xq5wEPSS: top 3%

    Django is subject to SQL injection through its column aliases

    Fixed in 5.1.12. Published Sep 8, 2025.

  2. CriticalCVE-2025-64459 on OSV.dev (opens in a new tab)GHSA-frmv-pr5f-9mcrEPSS: top 3%

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

    Fixed in 5.1.14. Published Nov 5, 2025.

  3. WarningCVE-2025-64460 on OSV.dev (opens in a new tab)GHSA-vrcr-9hj9-jcg6EPSS: top 19%

    Django is vulnerable to DoS via XML serializer text extraction

    Fixed in 5.1.15. Published Dec 2, 2025.

  4. CriticalCVE-2025-64458 on OSV.dev (opens in a new tab)GHSA-qw25-v68c-qjf3EPSS: top 21%

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

    Fixed in 5.1.14. Published Nov 5, 2025.

  5. CriticalCVE-2026-15307 on OSV.dev (opens in a new tab)GHSA-wvqv-fj8w-qmhmEPSS: top 35%

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

    Fixed in 5.2.17. Published Aug 4, 2026.

  6. WarningCVE-2026-15830 on OSV.dev (opens in a new tab)GHSA-q238-5cxm-5c9hEPSS: top 35%

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

    Fixed in 5.2.17. Published Aug 4, 2026.

  7. WarningCVE-2025-13372 on OSV.dev (opens in a new tab)GHSA-rqw2-ghq9-44m7EPSS: top 41%

    Django is vulnerable to SQL injection in column aliases

    Fixed in 5.1.15. Published Dec 2, 2025.

  8. LowCVE-2025-59682 on OSV.dev (opens in a new tab)GHSA-q95w-c7qg-hrffEPSS: top 41%

    Django vulnerable to partial directory traversal via archives

    Fixed in 5.1.13. Published Oct 1, 2025.

  9. CriticalCVE-2025-59681 on OSV.dev (opens in a new tab)GHSA-hpr9-3m2g-3j9pEPSS: top 52%

    Django vulnerable to SQL injection in column aliases

    Fixed in 5.1.13. Published Oct 1, 2025.

  10. WarningCVE-2026-53877 on OSV.dev (opens in a new tab)GHSA-crhf-3pfg-w68wEPSS: top 57%

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

    Fixed in 5.2.16. Published Jul 7, 2026.

  11. LowCVE-2026-48588 on OSV.dev (opens in a new tab)GHSA-3h9f-r86x-qvjxEPSS: top 65%

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

    Fixed in 5.2.16. Published Jul 7, 2026.

  12. LowCVE-2026-8404 on OSV.dev (opens in a new tab)GHSA-8cjm-8mp7-r2xfEPSS: top 65%

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

    Fixed in 5.2.15. Published Jun 3, 2026.

  13. LowCVE-2026-48587 on OSV.dev (opens in a new tab)GHSA-923m-gv2p-w5qpEPSS: top 65%

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

    Fixed in 5.2.15. Published Jun 3, 2026.

  14. WarningCVE-2026-53878 on OSV.dev (opens in a new tab)GHSA-8qcx-xf44-272xEPSS: top 76%

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

    Fixed in 5.2.16. Published Jul 7, 2026.

  15. LowCVE-2026-6873 on OSV.dev (opens in a new tab)GHSA-h7pc-vwp9-298gEPSS: top 81%

    Django: signed cookies are vulnerable to salt namespace collisions

    Fixed in 5.2.15. Published Jun 3, 2026.

Is Django the only one?

Paste a public GitHub repo or drop your requirements.txt or pyproject.toml and see every vulnerable, end-of-life or deprecated dependency, with one fix task. Free, no sign-up.

Check your whole repo

How this page is checked

StackPrism asks OSV.dev which advisories affect exactly Django 5.1.11, merges duplicates filed under several ids, and ranks them with CISA’s Known Exploited Vulnerabilities list and FIRST EPSS. Release dates and deprecation come from deps.dev and PyPI, support dates from endoflife.date. No AI writes this page: every sentence comes from that data, refreshed every few hours.

Last checked against PyPI, OSV.dev, deps.dev, CISA KEV, FIRST EPSS and endoflife.date.