PyPI package
Django 5.2.15 vulnerabilities, and the version that fixes all of them
Django 5.2.15 has 5 known vulnerabilities (1 rated high or critical); 5.2.17 fixes all of them.
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
- 5
- 1 rated high or critical
- Released
- Jun 3, 2026
- Latest is 6.1.2
- Django 5.2 support
- Supported
- Until Apr 30, 2028
- Licence
- BSD-3-Clause
- 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 5 known vulnerabilities. Released Aug 4, 2026.
No known vulnerabilitiesNewest 5.x release. Released Oct 6, 2026.
No known vulnerabilitiesLatest 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
- CriticalVulnerability
5 known vulnerabilities in django 5.2.15
1 rated high or critical. Most serious: CVE-2026-15307, Django GeoDjango spatial lookups allow file writes and outbound requests through GDAL raster parsing. Upgrading to 5.2.17 fixes all of them.
- LowOutdated
django 5.2.15 is 1 major version behind
Latest release is 6.1.2.
Every advisory for Django 5.2.15
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.
CriticalCVE-2026-15307 on OSV.dev (opens in a new tab)GHSA-wvqv-fj8w-qmhm
Django GeoDjango spatial lookups allow file writes and outbound requests through GDAL raster parsing
Fixed in 5.2.17. Published Aug 4, 2026.
WarningCVE-2026-15830 on OSV.dev (opens in a new tab)GHSA-q238-5cxm-5c9h
Django GeoDjango vulnerable to denial of service through deeply nested geometry collections
Fixed in 5.2.17. Published Aug 4, 2026.
WarningCVE-2026-53878 on OSV.dev (opens in a new tab)GHSA-8qcx-xf44-272x
Django: DomainNameValidator permits newline characters that may enable HTTP header injection
Fixed in 5.2.16. Published Jul 7, 2026.
WarningCVE-2026-53877 on OSV.dev (opens in a new tab)GHSA-crhf-3pfg-w68w
Django: GDALRaster may over-read heap memory when constructed from bytes
Fixed in 5.2.16. Published Jul 7, 2026.
LowCVE-2026-48588 on OSV.dev (opens in a new tab)GHSA-3h9f-r86x-qvjx
Django: cache middleware may expose private responses when unrelated request cookies are present
Fixed in 5.2.16. Published Jul 7, 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.
How this page is checked
StackPrism asks OSV.dev which advisories affect exactly Django 5.2.15, 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 (didn’t answer) and endoflife.date. Findings from that source may be missing; this page refreshes soon.