djangoproject vulnerabilities
Every vulnerability this feed holds for djangoproject, merged from five public registers and ordered by what warrants attention first — exploited in the wild, then CVSS, then recency.
6 vulnerabilities tracked.
- 6.9 An issue was discovered in Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19.
- 6.9 An issue was discovered in Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19.
- 6.9 An issue was discovered in Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19.
- 6.9 An issue was discovered in Django 6.1 before 6.1.3, 6.0.4 before 6.0.10, and 5.2.13 before 5.2.19.
- 2.3 An issue was discovered in Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19.
- 2.1 An issue was discovered in Django 6.1 before 6.1.3 and 6.0 before 6.0.10.
What this covers
This feed accumulates forward from the day it started storing records, and a name search that finds nothing here is also looked up against the registers directly — so an older advisory resolves even when it predates the corpus. It is still a reading view, not a substitute for the vendor's own advisory, and absence from this page is not a statement that djangoproject is free of vulnerabilities.
Query this from an agent over MCP · Check a lockfile by version
Other vendors tracked here
Google Microsoft Apple Red Hat zephyrproject Apache Software Foundation n/a Hewlett Packard Enterprise (HPE) MediaTek, Inc. Linux Eclipse Foundation Unknown FreeRDP Dell Tanium Oracle Corporation MONGODB Gitea WAVLINK Hitachi vercel vim jpadilla WSO2