CVE security advisories and vulnerability history for django.
django has 168 published CVE records since 2007, of which 0 are in CISA's Known Exploited Vulnerabilities catalog and 4 have a known public exploit. The average CVSS base score across scored CVEs is 7.0.
This page aggregates every publicly disclosed vulnerability (CVE) affecting django products, with severity breakdowns, the most-affected products, the most common weakness types, and the latest disclosures.
A quick read on django's vulnerability posture, as a share of its 168 published CVEs.
across 168 scored CVEs
87 of 168 scored
0 of 168 CVEs
4 of 168 CVEs
168 of 168 CVEs
How the CVSS severity of django's CVEs breaks down, plus how many are exploited in the wild or have public exploit code.
In CISA’s Known Exploited Vulnerabilities catalog
0
None of django's CVEs are currently listed in CISA's KEV catalog.
Public exploits
4
4 of django's CVEs have a known public exploit available.
The django products with the most published CVEs. Follow any product to browse its versions and vulnerabilities.
The CWE weakness categories most often found in django CVEs. Follow any weakness for its full explanation.
The CVE Numbering Authorities that publish django CVE records.
How many django CVEs were published each year.
The most recently disclosed vulnerabilities affecting django.
Track new django CVEs as they are disclosed and get AI-written analysis and remediation guidance.
Monitor django CVEsBrowse vulnerabilities for other tracked vendors.
Common questions about django vulnerabilities.
Vulnerability data is sourced from the CVE Program; severity, KEV, and exploit signals are aggregated by RadicalNotion.AI.
Monitor new django vulnerabilities as they are disclosed, with AI-written analysis and remediation guidance.
