SUSE · python310-Django4-4.2.17-1.1 on GA media
Affects SUSESource GCVE Database
Not known to be exploited · CVSS 7.5 High · fixed in SUSE package updates : patch SUSE django soon.
Data as of 16 Nov 2026, 00:19 UTC
- Patch
- Available – fixed in 5.1.4, 5.0.10, 4.2.17
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 6 Dec 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade django to 5.1.4, 5.0.10 or 4.2.17.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
PyPIdjangopkg:pypi/djangoOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
These are all security issues fixed in the python310-Django4-4.2.17-1.1 package on the GA media of openSUSE Tumbleweed.
References
- suse.com/support/security/rating/ (opens in a new tab)
- ftp.suse.com/pub/projects/security/csaf/2024/opensuse-su-2024_14565-1.json (opens in a new tab)
- lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/MHKGQNDWTHDRJRVCAHBUJ2GNSMMLYCOB/ (opens in a new tab)
- suse.com/security/cve/CVE-2024-53907/ (opens in a new tab)
- suse.com/security/cve/CVE-2024-53908/ (opens in a new tab)