← Search results
CVE-LINKED INVENTORY44 SECURITY RECORDS
djangoproject
Django
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This CVE identity is linked to the Lifecycle record Django. Use that record for publisher support phases and retirement dates.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-87975 | 6 Oct 2026 | Django: 6.1 < 6.1.2, 6.0 < 6.0.9, 5.2 < 5.2.18 | Django: 6.1.2, 6.0.9, 5.2.18 | Update reference ↗ |
| CVE-2026-87890 | 6 Oct 2026 | Django: 6.1 < 6.1.2, 6.0 < 6.0.9, 5.2 < 5.2.18 | Django: 6.1.2, 6.0.9, 5.2.18 | Update reference ↗ |
| CVE-2026-84429 | 6 Oct 2026 | Django: 6.1 < 6.1.2, 6.0 < 6.0.9, 5.2 < 5.2.18 | Django: 6.1.2, 6.0.9, 5.2.18 | Update reference ↗ |
| CVE-2026-77050 | 6 Oct 2026 | Django: 6.1 < 6.1.2, 6.0 < 6.0.9, 5.2 < 5.2.18 | Django: 6.1.2, 6.0.9, 5.2.18 | Update reference ↗ |
| CVE-2026-15920 | 4 Aug 2026 | 6.0 < 6.0.8; 5.2 < 5.2.17 | 6.0.8; 5.2.17 | Update reference ↗ |
| CVE-2026-15830 | 4 Aug 2026 | 6.0 < 6.0.8; 5.2 < 5.2.17 | 6.0.8; 5.2.17 | Update reference ↗ |
| CVE-2026-15337 | 4 Aug 2026 | 6.0 < 6.0.8; 5.2 < 5.2.17 | 6.0.8; 5.2.17 | Update reference ↗ |
| CVE-2026-15307 | 4 Aug 2026 | 6.0 < 6.0.8; 5.2 < 5.2.17 | 6.0.8; 5.2.17 | Update reference ↗ |
| CVE-2026-53878 | 7 Jul 2026 | 6.0 < 6.0.7; 5.2 < 5.2.16 | 6.0.7; 5.2.16 | Update reference ↗ |
| CVE-2026-53877 | 7 Jul 2026 | 6.0 < 6.0.7; 5.2 < 5.2.16 | 6.0.7; 5.2.16 | Update reference ↗ |
| CVE-2026-48588 | 7 Jul 2026 | 6.0 < 6.0.7; 5.2 < 5.2.16 | 6.0.7; 5.2.16 | Update reference ↗ |
| CVE-2026-48587 | 3 Jun 2026 | 6.0 < 6.0.6; 5.2 < 5.2.15 | 6.0.6; 5.2.15 | Update reference ↗ |
| CVE-2026-35193 | 3 Jun 2026 | 6.0 < 6.0.6; 5.2 < 5.2.15 | 6.0.6; 5.2.15 | Update reference ↗ |
| CVE-2026-8404 | 3 Jun 2026 | 6.0 < 6.0.6; 5.2 < 5.2.15 | 6.0.6; 5.2.15 | Update reference ↗ |
| CVE-2026-7666 | 3 Jun 2026 | 6.0 < 6.0.6; 5.2 < 5.2.15 | 6.0.6; 5.2.15 | Update reference ↗ |
| CVE-2026-6873 | 3 Jun 2026 | 6.0 < 6.0.6; 5.2 < 5.2.15 | 6.0.6; 5.2.15 | Update reference ↗ |
| CVE-2026-35192 | 5 May 2026 | 6.0 < 6.0.5; 5.2 < 5.2.14 | 6.0.5; 5.2.14 | Update reference ↗ |
| CVE-2026-6907 | 5 May 2026 | 6.0 < 6.0.5; 5.2 < 5.2.14 | 6.0.5; 5.2.14 | Update reference ↗ |
| CVE-2026-5766 | 5 May 2026 | 6.0 < 6.0.5; 5.2 < 5.2.14 | 6.0.5; 5.2.14 | Update reference ↗ |
| CVE-2026-33034 | 7 Apr 2026 | 6.0 < 6.0.4; 5.2 < 5.2.13; 4.2 < 4.2.30 | 6.0.4; 5.2.13; 4.2.30 | Update reference ↗ |
| CVE-2026-33033 | 7 Apr 2026 | 6.0 < 6.0.4; 5.2 < 5.2.13; 4.2 < 4.2.30 | 6.0.4; 5.2.13; 4.2.30 | Update reference ↗ |
| CVE-2026-4292 | 7 Apr 2026 | 6.0 < 6.0.4; 5.2 < 5.2.13; 4.2 < 4.2.30 | 6.0.4; 5.2.13; 4.2.30 | Update reference ↗ |
| CVE-2026-4277 | 7 Apr 2026 | 6.0 < 6.0.4; 5.2 < 5.2.13; 4.2 < 4.2.30 | 6.0.4; 5.2.13; 4.2.30 | Update reference ↗ |
| CVE-2026-3902 | 7 Apr 2026 | 6.0 < 6.0.4; 5.2 < 5.2.13; 4.2 < 4.2.30 | 6.0.4; 5.2.13; 4.2.30 | Update reference ↗ |
| CVE-2026-25674 | 3 Mar 2026 | 6.0 < 6.0.3; 5.2 < 5.2.12; 4.2 < 4.2.29 | 6.0.3; 5.2.12; 4.2.29 | Update reference ↗ |
| CVE-2026-25673 | 3 Mar 2026 | 6.0 < 6.0.3; 5.2 < 5.2.12; 4.2 < 4.2.29 | 6.0.3; 5.2.12; 4.2.29 | Update reference ↗ |
| CVE-2025-14550 | 3 Feb 2026 | 6.0 < 6.0.2; 5.2 < 5.2.11; 4.2 < 4.2.28; 3 < 3.11.1 | 6.0.2; 5.2.11; 4.2.28; 3.11.1 | Update reference ↗ |
| CVE-2026-1312 | 3 Feb 2026 | 6.0 < 6.0.2; 5.2 < 5.2.11; 4.2 < 4.2.28 | 6.0.2; 5.2.11; 4.2.28 | Update reference ↗ |
| CVE-2026-1287 | 3 Feb 2026 | 6.0 < 6.0.2; 5.2 < 5.2.11; 4.2 < 4.2.28 | 6.0.2; 5.2.11; 4.2.28 | Update reference ↗ |
| CVE-2026-1285 | 3 Feb 2026 | 6.0 < 6.0.2; 5.2 < 5.2.11; 4.2 < 4.2.28 | 6.0.2; 5.2.11; 4.2.28 | Update reference ↗ |
| CVE-2026-1207 | 3 Feb 2026 | 6.0 < 6.0.2; 5.2 < 5.2.11; 4.2 < 4.2.28 | 6.0.2; 5.2.11; 4.2.28 | Update reference ↗ |
| CVE-2025-13473 | 3 Feb 2026 | 6.0 < 6.0.2; 5.2 < 5.2.11; 4.2 < 4.2.28 | 6.0.2; 5.2.11; 4.2.28 | Update reference ↗ |
| CVE-2025-64460 | 2 Dec 2025 | 5.2 < 5.2.9; 5.1 < 5.1.15; 4.2 < 4.2.27 | 5.2.9; 5.1.15; 4.2.27 | Update reference ↗ |
| CVE-2025-13372 | 2 Dec 2025 | 5.2 < 5.2.9; 5.1 < 5.1.15; 4.2 < 4.2.27 | 5.2.9; 5.1.15; 4.2.27 | Update reference ↗ |
| CVE-2025-64459 | 5 Nov 2025 | 5.2 < 5.2.8; 5.1 < 5.1.14; 4.2 < 4.2.26 | 5.2.8; 5.1.14; 4.2.26 | Update reference ↗ |
| CVE-2025-64458 | 5 Nov 2025 | 5.2 < 5.2.8; 5.1 < 5.1.14; 4.2 < 4.2.26 | 5.2.8; 5.1.14; 4.2.26 | Update reference ↗ |
| CVE-2025-59682 | 1 Oct 2025 | 4.2 < 4.2.25; 5.1 < 5.1.13; 5.2 < 5.2.7 | Red Hat Ansible Automation Platform | Update reference ↗ |
| CVE-2025-59681 | 1 Oct 2025 | 4.2 < 4.2.25; 5.1 < 5.1.13; 5.2 < 5.2.7 | Red Hat Ansible Automation Platform | Update reference ↗ |
| CVE-2025-57833 | 3 Sep 2025 | 4.2 < 4.2.24; 5.1 < 5.1.12; 5.2 < 5.2.6 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-48432 | 5 Jun 2025 | 4.2 < 4.2.23; 5.1 < 5.1.11; 5.2 < 5.2.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-32873 | 8 May 2025 | 4.2 < 4.2.21; 5.1 < 5.1.9; 5.2 < 5.2.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-27556 | 2 Apr 2025 | 5.0 < 5.0.14; 5.1 < 5.1.8 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-26699 | 6 Mar 2025 | 4.2 < 4.2.20; 5.0 < 5.0.13; 5.1 < 5.1.7 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-56374 | 14 Jan 2025 | 4.2 < 4.2.18; 5.0 < 5.0.11; 5.1 < 5.1.5 | Red Hat Ansible Automation Platform | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.