@@ -96,41 +96,41 @@ Fixes for the following vulnerabilities are available in ELS for Django from Tux
9696
9797| CVE ID | Severity | Library | Vulnerable Versions | Safe Version |
9898| :------------: | :------: | :-----: | :-----------------: | :------------------: |
99- | CVE-2025 -57833 | High | django | 3.2.25 | 3.2.25.post1+tuxcare |
100- | CVE-2025 -64458 | High | django | 3.2.25 | 3.2.25.post2+tuxcare |
101- | CVE-2025 -64459 | Critical | django | 3.2.25 | 3.2.25.post2+tuxcare |
102- | CVE-2025 -48432 | Medium | django | 4.2 | 4.2.post1+tuxcare |
103- | CVE-2025 -48432 | Medium | django | 5.1.9 | 5.1.9.post1+tuxcare |
104- | CVE-2025 -27556 | High | django | 5.1 | 5.1.post2+tuxcare |
105- | CVE-2024 -56374 | Medium | django | 5.1.4 | 5.1.4.post1+tuxcare |
106- | CVE-2024 -53908 | N/A | django | 5.1 | 5.1.post3+tuxcare |
107- | CVE-2024 -53907 | N/A | django | 5.1 | 5.1.post3+tuxcare |
108- | CVE-2024 -45231 | N/A | django | 5.1 | 5.1.post2+tuxcare |
109- | CVE-2024 -45230 | N/A | django | 5.1 | 5.1.post3+tuxcare |
110- | CVE-2024 -42005 | High | django | 5.0 | 5.0.post5+tuxcare |
111- | CVE-2024 -41991 | N/A | django | 5.0.1 | 5.0.1.post2+tuxcare |
112- | CVE-2024 -41990 | High | django | 5.0 | 5.0.post5+tuxcare |
113- | CVE-2024 -41989 | High | django | 5.0.1 | 5.0.1.post3+tuxcare |
114- | CVE-2024 -39614 | N/A | django | 5.0 | 5.0.post2+tuxcare |
115- | CVE-2024 -39330 | N/A | django | 5.0 | 5.0.post4+tuxcare |
116- | CVE-2024 -39329 | N/A | django | 5.0.1 | 5.0.1.post2+tuxcare |
117- | CVE-2024 -38875 | N/A | django | 5.0 | 5.0.post3+tuxcare |
118- | CVE-2024 -27351 | Medium | django | 5.0.2 | 5.0.2.post1+tuxcare |
119- | CVE-2024 -24680 | High | django | 5.0 | 5.0.post1+tuxcare |
120- | CVE-2024 -24680 | High | django | 5.0.1 | 5.0.1.post1+tuxcare |
121- | CVE-2023 -24580 | High | django | 4.0 | 4.0.post1+tuxcare |
122- | CVE-2023 -23969 | High | django | 4.0 | 4.0.post1+tuxcare |
123- | CVE-2022 -41323 | High | django | 4.0 | 4.0.post2+tuxcare |
124- | CVE-2022 -41323 | High | django | 5.1 | 5.1.post1+tuxcare |
125- | CVE-2022 -36359 | High | django | 4.0 | 4.0.post3+tuxcare |
126- | CVE-2022 -34265 | Critical | django | 4.0 | 4.0.post3+tuxcare |
127- | CVE-2022 -28347 | Critical | django | 4.0 | 4.0.post3+tuxcare |
128- | CVE-2022 -28346 | Critical | django | 4.0 | 4.0.post4+tuxcare |
129- | CVE-2022 -23833 | High | django | 4.0 | 4.0.post6+tuxcare |
130- | CVE-2022 -22818 | Medium | django | 4.0 | 4.0.post5+tuxcare |
131- | CVE-2021 -45452 | Medium | django | 4.0 | 4.0.post4+tuxcare |
132- | CVE-2021 -45116 | High | django | 4.0 | 4.0.post2+tuxcare |
133- | CVE-2021 -45115 | High | django | 4.0 | 4.0.post4+tuxcare |
99+ | CVE-2025 -57833 | High | django | >= 3.2, < 3.2.25 | 3.2.25.post1+tuxcare |
100+ | CVE-2025 -64458 | High | django | >= 3.2, < 3.2.26 | 3.2.25.post2+tuxcare |
101+ | CVE-2025 -64459 | Critical | django | >= 3.2, < 3.2.26 | 3.2.25.post2+tuxcare |
102+ | CVE-2025 -48432 | Medium | django | >= 4.2, < 4.2.23 | 4.2.post1+tuxcare |
103+ | CVE-2025 -48432 | Medium | django | >= 5.1, < 5.1.11 | 5.1.9.post1+tuxcare |
104+ | CVE-2025 -27556 | High | django | >= 5.1, < 5.1.8 | 5.1.post2+tuxcare |
105+ | CVE-2024 -56374 | Medium | django | >= 5.1, < 5.1.5 | 5.1.4.post1+tuxcare |
106+ | CVE-2024 -53908 | N/A | django | >= 5.1, < 5.1.4 | 5.1.post3+tuxcare |
107+ | CVE-2024 -53907 | N/A | django | >= 5.1, < 5.1.4 | 5.1.post3+tuxcare |
108+ | CVE-2024 -45231 | N/A | django | >= 5.1, < 5.1.1 | 5.1.post2+tuxcare |
109+ | CVE-2024 -45230 | N/A | django | >= 5.1, < 5.1.1 | 5.1.post3+tuxcare |
110+ | CVE-2024 -42005 | High | django | >= 5.0, < 5.0.8 | 5.0.post5+tuxcare |
111+ | CVE-2024 -41991 | N/A | django | >= 5.0, < 5.0.8 | 5.0.1.post2+tuxcare |
112+ | CVE-2024 -41990 | High | django | >= 5.0, < 5.0.8 | 5.0.post5+tuxcare |
113+ | CVE-2024 -41989 | High | django | >= 5.0, < 5.0.8 | 5.0.1.post3+tuxcare |
114+ | CVE-2024 -39614 | N/A | django | >= 5.0, < 5.0.7 | 5.0.post2+tuxcare |
115+ | CVE-2024 -39330 | N/A | django | >= 5.0, < 5.0.7 | 5.0.post4+tuxcare |
116+ | CVE-2024 -39329 | N/A | django | >= 5.0, < 5.0.7 | 5.0.1.post2+tuxcare |
117+ | CVE-2024 -38875 | N/A | django | >= 5.0, < 5.0.7 | 5.0.post3+tuxcare |
118+ | CVE-2024 -27351 | Medium | django | >= 5.0, < 5.0.3 | 5.0.2.post1+tuxcare |
119+ | CVE-2024 -24680 | High | django | >= 5.0, < 5.0.2 | 5.0.post1+tuxcare |
120+ | CVE-2024 -24680 | High | django | >= 5.0, < 5.0.2 | 5.0.1.post1+tuxcare |
121+ | CVE-2023 -24580 | High | django | >= 4.0, < 4.0.10 | 4.0.post1+tuxcare |
122+ | CVE-2023 -23969 | High | django | >= 4.0, < 4.0.9 | 4.0.post1+tuxcare |
123+ | CVE-2022 -41323 | High | django | >= 4.0, < 4.0.8 | 4.0.post2+tuxcare |
124+ | CVE-2022 -41323 | High | django | >= 5.1, < 5.1.2 | 5.1.post1+tuxcare |
125+ | CVE-2022 -36359 | High | django | >= 4.0, < 4.0.7 | 4.0.post3+tuxcare |
126+ | CVE-2022 -34265 | Critical | django | >= 4.0, < 4.0.6 | 4.0.post3+tuxcare |
127+ | CVE-2022 -28347 | Critical | django | >= 4.0, < 4.0.4 | 4.0.post3+tuxcare |
128+ | CVE-2022 -28346 | Critical | django | >= 4.0, < 4.0.4 | 4.0.post4+tuxcare |
129+ | CVE-2022 -23833 | High | django | >= 4.0, < 4.0.2 | 4.0.post6+tuxcare |
130+ | CVE-2022 -22818 | Medium | django | >= 4.0, < 4.0.2 | 4.0.post5+tuxcare |
131+ | CVE-2021 -45452 | Medium | django | >= 4.0, < 4.0.1 | 4.0.post4+tuxcare |
132+ | CVE-2021 -45116 | High | django | >= 4.0, < 4.0.1 | 4.0.post2+tuxcare |
133+ | CVE-2021 -45115 | High | django | >= 4.0, < 4.0.1 | 4.0.post4+tuxcare |
134134
135135** N/A (Not Available)** means that the National Vulnerability Database (NVD) has registered this CVE, but an official CVSS severity score has not yet been assigned.
136136
0 commit comments