PyPI package
Django 5.2.17: no known vulnerabilities
Django 5.2.17 has no known vulnerabilities in OSV.dev.
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
- 0
- None in OSV.dev
- Released
- Aug 4, 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
Newer releases
5.2.17 has nothing to fix today. Newer releases, for when you upgrade:
Findings
- LowOutdated
django 5.2.17 is 1 major version behind
Latest release is 6.1.2.
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.17, 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 and endoflife.date.