| CVE-2026-33034 |
An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30
|
Not rated
|
Apr 7, 2026 |
| CVE-2026-33033 |
An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30
|
Not rated
|
Apr 7, 2026 |
| CVE-2026-4292 |
An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30
|
Not rated
|
Apr 7, 2026 |
| CVE-2026-4277 |
An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30
|
Not rated
|
Apr 7, 2026 |
| CVE-2026-3902 |
An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30
|
Not rated
|
Apr 7, 2026 |
| CVE-2026-25674 |
An issue was discovered in 6.0 before 6.0.3, 5.2 before 5.2.12, and 4.2 before 4.2.29
|
Not rated
|
Mar 3, 2026 |
| CVE-2026-25673 |
An issue was discovered in 6.0 before 6.0.3, 5.2 before 5.2.12, and 4.2 before 4.2.29
|
Not rated
|
Mar 3, 2026 |
| CVE-2025-14550 |
An issue was discovered in 6.0 before 6.0.2, 5.2 before 5.2.11, and 4.2 before 4.2.28
|
Not rated
|
Feb 3, 2026 |
| CVE-2026-1312 |
An issue was discovered in 6.0 before 6.0.2, 5.2 before 5.2.11, and 4.2 before 4.2.28
|
Not rated
|
Feb 3, 2026 |
| CVE-2026-1287 |
An issue was discovered in 6.0 before 6.0.2, 5.2 before 5.2.11, and 4.2 before 4.2.28
|
Not rated
|
Feb 3, 2026 |
| CVE-2026-1285 |
An issue was discovered in 6.0 before 6.0.2, 5.2 before 5.2.11, and 4.2 before 4.2.28
|
Not rated
|
Feb 3, 2026 |
| CVE-2026-1207 |
An issue was discovered in 6.0 before 6.0.2, 5.2 before 5.2.11, and 4.2 before 4.2.28
|
Not rated
|
Feb 3, 2026 |
| CVE-2025-13473 |
An issue was discovered in 6.0 before 6.0.2, 5.2 before 5.2.11, and 4.2 before 4.2.28
|
Not rated
|
Feb 3, 2026 |
| CVE-2025-64460 |
An issue was discovered in 5.2 before 5.2.9, 5.1 before 5.1.15, and 4.2 before 4.2.27
|
Not rated
|
Dec 2, 2025 |
| CVE-2025-13372 |
An issue was discovered in 5.2 before 5.2.9, 5.1 before 5.1.15, and 4.2 before 4.2.27
|
Not rated
|
Dec 2, 2025 |
| CVE-2025-64459 |
An issue was discovered in 5.1 before 5.1.14, 4.2 before 4.2.26, and 5.2 before 5.2.8
|
Not rated
|
Nov 5, 2025 |
| CVE-2025-64458 |
An issue was discovered in 5.1 before 5.1.14, 4.2 before 4.2.26, and 5.2 before 5.2.8
|
Not rated
|
Nov 5, 2025 |
| CVE-2025-59682 |
An issue was discovered in Django 4.2 before 4.2.25, 5.1 before 5.1.13, and 5.2 before 5.2.7
|
3.1
Low
|
Oct 1, 2025 |
| CVE-2025-59681 |
An issue was discovered in Django 4.2 before 4.2.25, 5.1 before 5.1.13, and 5.2 before 5.2.7
|
7.1
High
|
Oct 1, 2025 |
| CVE-2025-57833 |
An issue was discovered in Django 4.2 before 4.2.24, 5.1 before 5.1.12, and 5.2 before 5.2.6
|
7.1
High
|
Sep 3, 2025 |
| CVE-2025-48432 |
An issue was discovered in Django 5.2 before 5.2.3, 5.1 before 5.1.11, and 4.2 before 4.2.23
|
4.0
Medium
|
Jun 5, 2025 |
| CVE-2025-32873 |
An issue was discovered in Django 4.2 before 4.2.21, 5.1 before 5.1.9, and 5.2 before 5.2.1
|
5.3
Medium
|
May 8, 2025 |
| CVE-2025-27556 |
An issue was discovered in Django 5.1 before 5.1.8 and 5.0 before 5.0.14
|
5.8
Medium
|
Apr 2, 2025 |
| CVE-2025-26699 |
An issue was discovered in Django 5.1 before 5.1.7, 5.0 before 5.0.13, and 4.2 before 4.2.20
|
5.0
Medium
|
Mar 6, 2025 |
| CVE-2024-56374 |
An issue was discovered in Django 5.1 before 5.1.5, 5.0 before 5.0.11, and 4.2 before 4.2.18
|
5.8
Medium
|
Jan 14, 2025 |