Vulnerability Database · PyPI · django · Version
django 5.2.0rc1
5.2.0rc1 is affected by 47 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 6.1.2.
Critical 1 High 5 Medium 12 Low 5 Unrated 24
-
Released 19 Mar 2025
Licence BSD-3-Clause
Also known from other sources 21
Newer releases 300
Database updated 23/Oct/2026
Release and licence data published by PyPI. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
django 5.2.0rc1 vulnerabilities
47 vulnerabilities cover django 5.2.0rc1. Scroll the table for all of them, or open the full list in the database.
Looking for another version, or everything Vulert holds for django?
Questions
About django 5.2.0rc1
Is django 5.2.0rc1 vulnerable?
Yes. 47 vulnerabilities in the Vulert database cover django 5.2.0rc1: 1 critical, 5 high, 12 medium and 5 low, plus 24 not yet rated. The upgrade Vulert recommends is 6.1.2, and each entry above names the fixed version to move to.
Which version of django should I use instead of 5.2.0rc1?
6.1.2 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 5.2.0rc1 the latest release of django?
No. 5.2.0rc1 was published 19 Mar 2025, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor django for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the django version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.