{ "@id": "urn:uuid:77c3b513-3da0-4d69-b2ad-8d092b8c9cd7", "role": "Document Creator", "author": "https://tuxcare.com", "version": 15, "@context": "https://openvex.dev/ns/v0.2.0", "timestamp": "2026-10-29T20:44:00.091011+00:00", "statements": [ { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-28T19:05:19.418788+00:00", "status_notes": "Vulnerability CVE-2021-45115 affects version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2021-45115" }, "action_statement": "Vulnerability CVE-2021-45115 affects version 5.1.post3+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-28T19:05:19.418788+00:00", "status_notes": "Vulnerability CVE-2021-45116 affects version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2021-45116" }, "action_statement": "Vulnerability CVE-2021-45116 affects version 5.1.post3+tuxcare of django." }, { "status": "not_affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-29T19:05:08.405699+00:00", "status_notes": "Vulnerability CVE-2021-45452 does not affect version 5.1.post3+tuxcare of django. not_affected \u2014 CVE-2021-45452 affects Django 2.2 before 2.2.26, 3.2 before 3.2.11, and 4.0 before 4.0.1. The target repository is Django 5.1.post14+tuxcare, which includes the upstream fix from commit 6d343d01c5 (Dec 2021) by Florian Apolloner. All required defenses are present: backslash normalization, path traversal detection for \"..\" sequences, validate_file_name() calls throughout the save path, and os.pa...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2021-45452" }, "impact_statement": "not_affected \u2014 CVE-2021-45452 affects Django 2.2 before 2.2.26, 3.2 before 3.2.11, and 4.0 before 4.0.1. The target repository is Django 5.1.post14+tuxcare, which includes the upstream fix from commit 6d343d01c5 (Dec 2021) by Florian Apolloner. All required defenses are present: backslash normalization, path traversal detection for \"..\" sequences, validate_file_name() calls throughout the save path, and os.pa..." }, { "status": "not_affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-29T19:53:47.658121+00:00", "status_notes": "Vulnerability CVE-2022-22818 does not affect version 5.1.post3+tuxcare of django. not_affected \u2014 The target Django 5.1.post14+tuxcare repository is NOT AFFECTED by CVE-2022-22818. The vulnerability (XSS via unescaped output in the {% debug %} template tag) was fixed in upstream Django commit 394517f078 on January 2, 2022, over 3 years before TuxCare began maintaining this version. The fix is present in the current code: django/template/defaulttags.py lines 120-131 show the DebugNode.render...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2022-22818" }, "impact_statement": "not_affected \u2014 The target Django 5.1.post14+tuxcare repository is NOT AFFECTED by CVE-2022-22818. The vulnerability (XSS via unescaped output in the {% debug %} template tag) was fixed in upstream Django commit 394517f078 on January 2, 2022, over 3 years before TuxCare began maintaining this version. The fix is present in the current code: django/template/defaulttags.py lines 120-131 show the DebugNode.render..." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-28T19:06:21.253116+00:00", "status_notes": "Vulnerability CVE-2022-23833 affects version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2022-23833" }, "action_statement": "Vulnerability CVE-2022-23833 affects version 5.1.post3+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-28T19:06:21.253116+00:00", "status_notes": "Vulnerability CVE-2022-28346 affects version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2022-28346" }, "action_statement": "Vulnerability CVE-2022-28346 affects version 5.1.post3+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-28T19:06:21.253116+00:00", "status_notes": "Vulnerability CVE-2022-28347 affects version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2022-28347" }, "action_statement": "Vulnerability CVE-2022-28347 affects version 5.1.post3+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-28T19:08:06.540752+00:00", "status_notes": "Vulnerability CVE-2022-34265 affects version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2022-34265" }, "action_statement": "Vulnerability CVE-2022-34265 affects version 5.1.post3+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-28T19:08:06.540752+00:00", "status_notes": "Vulnerability CVE-2022-36359 affects version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2022-36359" }, "action_statement": "Vulnerability CVE-2022-36359 affects version 5.1.post3+tuxcare of django." }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2022-41323 is fixed in version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2022-41323" } }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-28T19:08:06.540752+00:00", "status_notes": "Vulnerability CVE-2023-23969 affects version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2023-23969" }, "action_statement": "Vulnerability CVE-2023-23969 affects version 5.1.post3+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-28T19:05:19.418788+00:00", "status_notes": "Vulnerability CVE-2023-24580 affects version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2023-24580" }, "action_statement": "Vulnerability CVE-2023-24580 affects version 5.1.post3+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-28T19:07:12.211534+00:00", "status_notes": "Vulnerability CVE-2023-31047 affects version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2023-31047" }, "action_statement": "Vulnerability CVE-2023-31047 affects version 5.1.post3+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-28T19:06:21.253116+00:00", "status_notes": "Vulnerability CVE-2023-36053 affects version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2023-36053" }, "action_statement": "Vulnerability CVE-2023-36053 affects version 5.1.post3+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-28T19:23:04.118629+00:00", "status_notes": "Vulnerability CVE-2023-41164 affects version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2023-41164" }, "action_statement": "Vulnerability CVE-2023-41164 affects version 5.1.post3+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-28T19:23:04.118629+00:00", "status_notes": "Vulnerability CVE-2023-43665 affects version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2023-43665" }, "action_statement": "Vulnerability CVE-2023-43665 affects version 5.1.post3+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-28T19:23:04.118629+00:00", "status_notes": "Vulnerability CVE-2023-46695 affects version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2023-46695" }, "action_statement": "Vulnerability CVE-2023-46695 affects version 5.1.post3+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-28T19:09:04.720419+00:00", "status_notes": "Vulnerability CVE-2024-24680 affects version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2024-24680" }, "action_statement": "Vulnerability CVE-2024-24680 affects version 5.1.post3+tuxcare of django." }, { "status": "not_affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-29T20:15:06.276027+00:00", "status_notes": "Vulnerability CVE-2024-27351 does not affect version 5.1.post3+tuxcare of django. not_affected \u2014 Django 5.1.0.post14+tuxcare is NOT affected by CVE-2024-27351. The target uses an HTMLParser-based architecture (introduced upstream in commit 6ee37ada32 on 2023-01-03) that completely replaced the vulnerable regex-based HTML truncation. The vulnerable regex pattern r\"<[^>]+?>|([^<>\\s]+)\" that causes ReDoS on inputs like \"<<<...\" is absent from this version. CVE-2024-27351 only affects Django 3...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2024-27351" }, "impact_statement": "not_affected \u2014 Django 5.1.0.post14+tuxcare is NOT affected by CVE-2024-27351. The target uses an HTMLParser-based architecture (introduced upstream in commit 6ee37ada32 on 2023-01-03) that completely replaced the vulnerable regex-based HTML truncation. The vulnerable regex pattern r\"<[^>]+?>|([^<>\\s]+)\" that causes ReDoS on inputs like \"<<<...\" is absent from this version. CVE-2024-27351 only affects Django 3..." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-28T19:05:19.418788+00:00", "status_notes": "Vulnerability CVE-2024-38875 affects version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2024-38875" }, "action_statement": "Vulnerability CVE-2024-38875 affects version 5.1.post3+tuxcare of django." }, { "status": "not_affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-29T19:11:13.694200+00:00", "status_notes": "Vulnerability CVE-2024-39329 does not affect version 5.1.post3+tuxcare of django. not_affected \u2014 CVE-2024-39329 affects Django's ModelBackend.authenticate() method, allowing user enumeration via timing attacks on users with unusable passwords. The target repository (Django 5.1.post14+tuxcare) is NOT AFFECTED because the upstream fix (commit f5d16483f3) was already present in Django 5.1 release before TuxCare's onboarding. The fix adds a computationally expensive make_password() call when c...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2024-39329" }, "impact_statement": "not_affected \u2014 CVE-2024-39329 affects Django's ModelBackend.authenticate() method, allowing user enumeration via timing attacks on users with unusable passwords. The target repository (Django 5.1.post14+tuxcare) is NOT AFFECTED because the upstream fix (commit f5d16483f3) was already present in Django 5.1 release before TuxCare's onboarding. The fix adds a computationally expensive make_password() call when c..." }, { "status": "not_affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-29T20:44:00.091011+00:00", "status_notes": "Vulnerability CVE-2024-39330 does not affect version 5.1.post3+tuxcare of django. not_affected \u2014 CVE-2024-39330 directory traversal vulnerability is NOT present in Django 5.1 at commit 8ba232230f. The fix was already included in the upstream Django 5.1.x release that TuxCare started from. The upstream commit 6d36203648 (authored by Natalia from Django core team) added three validation points in Storage.save() and backslash normalization in validate_file_name(), all of which are present in ...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2024-39330" }, "impact_statement": "not_affected \u2014 CVE-2024-39330 directory traversal vulnerability is NOT present in Django 5.1 at commit 8ba232230f. The fix was already included in the upstream Django 5.1.x release that TuxCare started from. The upstream commit 6d36203648 (authored by Natalia from Django core team) added three validation points in Storage.save() and backslash normalization in validate_file_name(), all of which are present in ..." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-28T19:07:12.211534+00:00", "status_notes": "Vulnerability CVE-2024-39614 affects version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2024-39614" }, "action_statement": "Vulnerability CVE-2024-39614 affects version 5.1.post3+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-28T19:07:12.211534+00:00", "status_notes": "Vulnerability CVE-2024-41989 affects version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2024-41989" }, "action_statement": "Vulnerability CVE-2024-41989 affects version 5.1.post3+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-28T19:05:19.418788+00:00", "status_notes": "Vulnerability CVE-2024-41990 affects version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2024-41990" }, "action_statement": "Vulnerability CVE-2024-41990 affects version 5.1.post3+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-28T19:08:06.540752+00:00", "status_notes": "Vulnerability CVE-2024-41991 affects version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2024-41991" }, "action_statement": "Vulnerability CVE-2024-41991 affects version 5.1.post3+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-28T19:05:19.418788+00:00", "status_notes": "Vulnerability CVE-2024-42005 affects version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2024-42005" }, "action_statement": "Vulnerability CVE-2024-42005 affects version 5.1.post3+tuxcare of django." }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2024-45230 is fixed in version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2024-45230" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2024-45231 is fixed in version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2024-45231" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2024-53907 is fixed in version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2024-53907" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2024-53908 is fixed in version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2024-53908" } }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2024-56374 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post6+tuxcare.", "vulnerability": { "name": "CVE-2024-56374" }, "action_statement": "Vulnerability CVE-2024-56374 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post6+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2025-13372 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post10+tuxcare.", "vulnerability": { "name": "CVE-2025-13372" }, "action_statement": "Vulnerability CVE-2025-13372 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post10+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2025-13473 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post7+tuxcare.", "vulnerability": { "name": "CVE-2025-13473" }, "action_statement": "Vulnerability CVE-2025-13473 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post7+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2025-14550 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post7+tuxcare.", "vulnerability": { "name": "CVE-2025-14550" }, "action_statement": "Vulnerability CVE-2025-14550 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post7+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2025-26699 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post10+tuxcare.", "vulnerability": { "name": "CVE-2025-26699" }, "action_statement": "Vulnerability CVE-2025-26699 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post10+tuxcare." }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2025-27556 is fixed in version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2025-27556" } }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2025-32873 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post4+tuxcare.", "vulnerability": { "name": "CVE-2025-32873" }, "action_statement": "Vulnerability CVE-2025-32873 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post4+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2025-48432 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post6+tuxcare.", "vulnerability": { "name": "CVE-2025-48432" }, "action_statement": "Vulnerability CVE-2025-48432 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post6+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2025-57833 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post9+tuxcare.", "vulnerability": { "name": "CVE-2025-57833" }, "action_statement": "Vulnerability CVE-2025-57833 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post9+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2025-59681 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post5+tuxcare.", "vulnerability": { "name": "CVE-2025-59681" }, "action_statement": "Vulnerability CVE-2025-59681 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post5+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2025-59682 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post10+tuxcare.", "vulnerability": { "name": "CVE-2025-59682" }, "action_statement": "Vulnerability CVE-2025-59682 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post10+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2025-64458 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post5+tuxcare.", "vulnerability": { "name": "CVE-2025-64458" }, "action_statement": "Vulnerability CVE-2025-64458 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post5+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2025-64459 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post4+tuxcare.", "vulnerability": { "name": "CVE-2025-64459" }, "action_statement": "Vulnerability CVE-2025-64459 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post4+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2025-64460 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post5+tuxcare.", "vulnerability": { "name": "CVE-2025-64460" }, "action_statement": "Vulnerability CVE-2025-64460 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post5+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-1207 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post5+tuxcare.", "vulnerability": { "name": "CVE-2026-1207" }, "action_statement": "Vulnerability CVE-2026-1207 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post5+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-1285 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post8+tuxcare.", "vulnerability": { "name": "CVE-2026-1285" }, "action_statement": "Vulnerability CVE-2026-1285 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post8+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-1287 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post7+tuxcare.", "vulnerability": { "name": "CVE-2026-1287" }, "action_statement": "Vulnerability CVE-2026-1287 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post7+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-1312 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post5+tuxcare.", "vulnerability": { "name": "CVE-2026-1312" }, "action_statement": "Vulnerability CVE-2026-1312 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post5+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-01T09:09:01.183793+00:00", "status_notes": "Vulnerability CVE-2026-15307 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post11+tuxcare.", "vulnerability": { "name": "CVE-2026-15307" }, "action_statement": "Vulnerability CVE-2026-15307 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post11+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-01T09:09:01.183793+00:00", "status_notes": "Vulnerability CVE-2026-15830 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post11+tuxcare.", "vulnerability": { "name": "CVE-2026-15830" }, "action_statement": "Vulnerability CVE-2026-15830 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post11+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-28T19:06:21.253116+00:00", "status_notes": "Vulnerability CVE-2026-25673 affects version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2026-25673" }, "action_statement": "Vulnerability CVE-2026-25673 affects version 5.1.post3+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-28T19:09:04.720419+00:00", "status_notes": "Vulnerability CVE-2026-25674 affects version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2026-25674" }, "action_statement": "Vulnerability CVE-2026-25674 affects version 5.1.post3+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-28T19:07:12.211534+00:00", "status_notes": "Vulnerability CVE-2026-33033 affects version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2026-33033" }, "action_statement": "Vulnerability CVE-2026-33033 affects version 5.1.post3+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-28T19:05:19.418788+00:00", "status_notes": "Vulnerability CVE-2026-33034 affects version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2026-33034" }, "action_statement": "Vulnerability CVE-2026-33034 affects version 5.1.post3+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-28T19:09:04.720419+00:00", "status_notes": "Vulnerability CVE-2026-3902 affects version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2026-3902" }, "action_statement": "Vulnerability CVE-2026-3902 affects version 5.1.post3+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-28T19:08:06.540752+00:00", "status_notes": "Vulnerability CVE-2026-4277 affects version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2026-4277" }, "action_statement": "Vulnerability CVE-2026-4277 affects version 5.1.post3+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-10-28T19:06:21.253116+00:00", "status_notes": "Vulnerability CVE-2026-4292 affects version 5.1.post3+tuxcare of django.", "vulnerability": { "name": "CVE-2026-4292" }, "action_statement": "Vulnerability CVE-2026-4292 affects version 5.1.post3+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-48587 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post5+tuxcare.", "vulnerability": { "name": "CVE-2026-48587" }, "action_statement": "Vulnerability CVE-2026-48587 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post5+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-48588 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post5+tuxcare.", "vulnerability": { "name": "CVE-2026-48588" }, "action_statement": "Vulnerability CVE-2026-48588 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post5+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-53877 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post5+tuxcare.", "vulnerability": { "name": "CVE-2026-53877" }, "action_statement": "Vulnerability CVE-2026-53877 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post5+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-53878 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post5+tuxcare.", "vulnerability": { "name": "CVE-2026-53878" }, "action_statement": "Vulnerability CVE-2026-53878 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post5+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-6873 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post5+tuxcare.", "vulnerability": { "name": "CVE-2026-6873" }, "action_statement": "Vulnerability CVE-2026-6873 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post5+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.post3+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.post3+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-8404 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post5+tuxcare.", "vulnerability": { "name": "CVE-2026-8404" }, "action_statement": "Vulnerability CVE-2026-8404 affects version 5.1.post3+tuxcare of django, and is fixed in 5.1.post5+tuxcare." } ] }