Linux · 
openSUSE Leap · Security advisory · February 7, 2026
openSUSE Leap · Security advisory · February 7, 2026OPENSUSE-SU-2026:20184-1: python-Django security update
OPENSUSE-SU-2026:20184-1, released February 7, 2026, fixes 6 CVEs in python-Django (version 5.2.4-bp160.5.1). None of them is reported as exploited. Patch Radar priority: High.
High
CVEs closed
6
None rated Critical
Exploited
0
None reported
Highest CVSS
7.5
Base score, 0 to 10
Highest EPSS
0.1282
96th percentile
Priority of the 6 CVEs
Patch now 0
Urgent 0
High 2
Routine 4
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| python-Django | opensuse-leap 16.0 | 5.2.4-bp160.5.1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| High | CVE-2025-14550 | python-Django: This update for python-Django fixes the following issues: - CVE-2025-14550: Fixed potential denial-of-service via re... | 7.5 | 0.0111 | None reported |
| High | CVE-2026-1285 | python-django: An issue was discovered in 6.0 before 6.0.2, 5.2 before 5.2.11, and 4.2 before 4.2.28 | 7.5 | 0.0111 | None reported |
| Routine | CVE-2026-1207 | python-django: An issue was discovered in 6.0 before 6.0.2, 5.2 before 5.2.11, and 4.2 before 4.2.28 | 5.4 | 0.1282 | None reported |
| Routine | CVE-2026-1312 | python-django: An issue was discovered in 6.0 before 6.0.2, 5.2 before 5.2.11, and 4.2 before 4.2.28 | 5.4 | 0.0090 | None reported |
| Routine | CVE-2026-1287 | python-django: An issue was discovered in 6.0 before 6.0.2, 5.2 before 5.2.11, and 4.2 before 4.2.28 | 5.4 | 0.0084 | None reported |
| Routine | CVE-2025-13473 | python3-django: An issue was discovered in 6.0 before 6.0.2, 5.2 before 5.2.11, and 4.2 before 4.2.28 | 5.3 | 0.0080 | None reported |
Showing 1 to 6 of 6
1
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.