{ "@id": "urn:uuid:6239e77d-c848-457a-a4f4-b7a8dc436f7c", "role": "Document Creator", "author": "https://tuxcare.com", "version": 13, "@context": "https://openvex.dev/ns/v0.2.0", "timestamp": "2026-10-29T19:54:58.809918+00:00", "statements": [ { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-28T19:05:19.418788+00:00", "status_notes": "Vulnerability CVE-2021-45115 affects version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2021-45115" }, "action_statement": "Vulnerability CVE-2021-45115 affects version 5.0.2.post5+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-28T19:05:19.418788+00:00", "status_notes": "Vulnerability CVE-2021-45116 affects version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2021-45116" }, "action_statement": "Vulnerability CVE-2021-45116 affects version 5.0.2.post5+tuxcare of django." }, { "status": "not_affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-29T19:06:40.250315+00:00", "status_notes": "Vulnerability CVE-2021-45452 does not affect version 5.0.2.post5+tuxcare of django. not_affected \u2014 Django 5.0.2 is NOT affected by CVE-2021-45452. The directory traversal vulnerability in Storage.save() was fixed by upstream Django in version 4.0.1 (January 2022), over 2 years before Django 5.0.2 was released (February 2024). All required defenses are present in the target: backslash normalization, path traversal detection via \"..\" checks, os.path.relpath() to ensure relative paths, and trip...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2021-45452" }, "impact_statement": "not_affected \u2014 Django 5.0.2 is NOT affected by CVE-2021-45452. The directory traversal vulnerability in Storage.save() was fixed by upstream Django in version 4.0.1 (January 2022), over 2 years before Django 5.0.2 was released (February 2024). All required defenses are present in the target: backslash normalization, path traversal detection via \"..\" checks, os.path.relpath() to ensure relative paths, and trip..." }, { "status": "not_affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-29T19:54:58.809918+00:00", "status_notes": "Vulnerability CVE-2022-22818 does not affect version 5.0.2.post5+tuxcare of django. not_affected \u2014 Target Django 5.0.2 is not affected by CVE-2022-22818. The vulnerability (unescaped HTML output in {% debug %} template tag leading to XSS) is not present because the upstream Django fix was already included in the 5.0.2 release. The DebugNode.render() method contains both security measures: (1) early return when DEBUG=False, and (2) HTML escaping via escape() on all pformat outputs. CVE affect...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2022-22818" }, "impact_statement": "not_affected \u2014 Target Django 5.0.2 is not affected by CVE-2022-22818. The vulnerability (unescaped HTML output in {% debug %} template tag leading to XSS) is not present because the upstream Django fix was already included in the 5.0.2 release. The DebugNode.render() method contains both security measures: (1) early return when DEBUG=False, and (2) HTML escaping via escape() on all pformat outputs. CVE affect..." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-28T19:06:21.253116+00:00", "status_notes": "Vulnerability CVE-2022-23833 affects version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2022-23833" }, "action_statement": "Vulnerability CVE-2022-23833 affects version 5.0.2.post5+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-28T19:06:21.253116+00:00", "status_notes": "Vulnerability CVE-2022-28346 affects version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2022-28346" }, "action_statement": "Vulnerability CVE-2022-28346 affects version 5.0.2.post5+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-28T19:06:21.253116+00:00", "status_notes": "Vulnerability CVE-2022-28347 affects version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2022-28347" }, "action_statement": "Vulnerability CVE-2022-28347 affects version 5.0.2.post5+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-28T19:08:06.540752+00:00", "status_notes": "Vulnerability CVE-2022-34265 affects version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2022-34265" }, "action_statement": "Vulnerability CVE-2022-34265 affects version 5.0.2.post5+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-28T19:08:06.540752+00:00", "status_notes": "Vulnerability CVE-2022-36359 affects version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2022-36359" }, "action_statement": "Vulnerability CVE-2022-36359 affects version 5.0.2.post5+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-28T19:07:12.211534+00:00", "status_notes": "Vulnerability CVE-2022-41323 affects version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2022-41323" }, "action_statement": "Vulnerability CVE-2022-41323 affects version 5.0.2.post5+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-28T19:08:06.540752+00:00", "status_notes": "Vulnerability CVE-2023-23969 affects version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2023-23969" }, "action_statement": "Vulnerability CVE-2023-23969 affects version 5.0.2.post5+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-28T19:05:19.418788+00:00", "status_notes": "Vulnerability CVE-2023-24580 affects version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2023-24580" }, "action_statement": "Vulnerability CVE-2023-24580 affects version 5.0.2.post5+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-28T19:07:12.211534+00:00", "status_notes": "Vulnerability CVE-2023-31047 affects version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2023-31047" }, "action_statement": "Vulnerability CVE-2023-31047 affects version 5.0.2.post5+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-28T19:06:21.253116+00:00", "status_notes": "Vulnerability CVE-2023-36053 affects version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2023-36053" }, "action_statement": "Vulnerability CVE-2023-36053 affects version 5.0.2.post5+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-28T19:23:04.118629+00:00", "status_notes": "Vulnerability CVE-2023-41164 affects version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2023-41164" }, "action_statement": "Vulnerability CVE-2023-41164 affects version 5.0.2.post5+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-28T19:23:04.118629+00:00", "status_notes": "Vulnerability CVE-2023-43665 affects version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2023-43665" }, "action_statement": "Vulnerability CVE-2023-43665 affects version 5.0.2.post5+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-28T19:23:04.118629+00:00", "status_notes": "Vulnerability CVE-2023-46695 affects version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2023-46695" }, "action_statement": "Vulnerability CVE-2023-46695 affects version 5.0.2.post5+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-28T19:09:04.720419+00:00", "status_notes": "Vulnerability CVE-2024-24680 affects version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2024-24680" }, "action_statement": "Vulnerability CVE-2024-24680 affects version 5.0.2.post5+tuxcare of django." }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2024-27351 is fixed in version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2024-27351" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2024-38875 is fixed in version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2024-38875" } }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2024-39329 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post6+tuxcare.", "vulnerability": { "name": "CVE-2024-39329" }, "action_statement": "Vulnerability CVE-2024-39329 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post6+tuxcare." }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2024-39330 is fixed in version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2024-39330" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2024-39614 is fixed in version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2024-39614" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2024-41989 is fixed in version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2024-41989" } }, { "status": "not_affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2024-41990 does not affect version 5.0.2.post5+tuxcare of django. not_affected \u2014 Django 5.0.2 uses the original simple trim_punctuation implementation that lacks the vulnerable code pattern. CVE-2024-41990's DoS vulnerability was introduced by the CVE-2024-38875 fix (commit d666457453, June 2024) which replaced the simple implementation with a complex CountsDict-based one containing repeated rfind('&') calls. The target version predates this architectural change and therefo...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2024-41990" }, "impact_statement": "not_affected \u2014 Django 5.0.2 uses the original simple trim_punctuation implementation that lacks the vulnerable code pattern. CVE-2024-41990's DoS vulnerability was introduced by the CVE-2024-38875 fix (commit d666457453, June 2024) which replaced the simple implementation with a complex CountsDict-based one containing repeated rfind('&') calls. The target version predates this architectural change and therefo..." }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2024-41991 is fixed in version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2024-41991" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2024-42005 is fixed in version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2024-42005" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2024-45230 is fixed in version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2024-45230" } }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2024-45231 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post7+tuxcare.", "vulnerability": { "name": "CVE-2024-45231" }, "action_statement": "Vulnerability CVE-2024-45231 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post7+tuxcare." }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2024-53907 is fixed in version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2024-53907" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2024-53908 is fixed in version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2024-53908" } }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2024-56374 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post6+tuxcare.", "vulnerability": { "name": "CVE-2024-56374" }, "action_statement": "Vulnerability CVE-2024-56374 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post6+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2025-13372 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post9+tuxcare.", "vulnerability": { "name": "CVE-2025-13372" }, "action_statement": "Vulnerability CVE-2025-13372 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post9+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2025-13473 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post8+tuxcare.", "vulnerability": { "name": "CVE-2025-13473" }, "action_statement": "Vulnerability CVE-2025-13473 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post8+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2025-14550 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post8+tuxcare.", "vulnerability": { "name": "CVE-2025-14550" }, "action_statement": "Vulnerability CVE-2025-14550 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post8+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2025-26699 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post6+tuxcare.", "vulnerability": { "name": "CVE-2025-26699" }, "action_statement": "Vulnerability CVE-2025-26699 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post6+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2025-27556 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post6+tuxcare.", "vulnerability": { "name": "CVE-2025-27556" }, "action_statement": "Vulnerability CVE-2025-27556 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post6+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-28T19:09:04.720419+00:00", "status_notes": "Vulnerability CVE-2025-32873 affects version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2025-32873" }, "action_statement": "Vulnerability CVE-2025-32873 affects version 5.0.2.post5+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2025-48432 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post7+tuxcare.", "vulnerability": { "name": "CVE-2025-48432" }, "action_statement": "Vulnerability CVE-2025-48432 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post7+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-01T04:50:02.038518+00:00", "status_notes": "Vulnerability CVE-2025-57833 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post10+tuxcare.", "vulnerability": { "name": "CVE-2025-57833" }, "action_statement": "Vulnerability CVE-2025-57833 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post10+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-28T19:08:06.540752+00:00", "status_notes": "Vulnerability CVE-2025-59681 affects version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2025-59681" }, "action_statement": "Vulnerability CVE-2025-59681 affects version 5.0.2.post5+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-28T19:06:21.253116+00:00", "status_notes": "Vulnerability CVE-2025-59682 affects version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2025-59682" }, "action_statement": "Vulnerability CVE-2025-59682 affects version 5.0.2.post5+tuxcare of django." }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2025-64458 is fixed in version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2025-64458" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2025-64459 is fixed in version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2025-64459" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2025-64460 is fixed in version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2025-64460" } }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-1207 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post6+tuxcare.", "vulnerability": { "name": "CVE-2026-1207" }, "action_statement": "Vulnerability CVE-2026-1207 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post6+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-06T09:18:00.239158+00:00", "status_notes": "Vulnerability CVE-2026-1285 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post12+tuxcare.", "vulnerability": { "name": "CVE-2026-1285" }, "action_statement": "Vulnerability CVE-2026-1285 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post12+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-1287 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post8+tuxcare.", "vulnerability": { "name": "CVE-2026-1287" }, "action_statement": "Vulnerability CVE-2026-1287 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post8+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-1312 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post6+tuxcare.", "vulnerability": { "name": "CVE-2026-1312" }, "action_statement": "Vulnerability CVE-2026-1312 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post6+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-06T09:18:00.239158+00:00", "status_notes": "Vulnerability CVE-2026-15307 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post11+tuxcare.", "vulnerability": { "name": "CVE-2026-15307" }, "action_statement": "Vulnerability CVE-2026-15307 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post11+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-06T09:18:00.239158+00:00", "status_notes": "Vulnerability CVE-2026-15830 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post11+tuxcare.", "vulnerability": { "name": "CVE-2026-15830" }, "action_statement": "Vulnerability CVE-2026-15830 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post11+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-28T19:06:21.253116+00:00", "status_notes": "Vulnerability CVE-2026-25673 affects version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2026-25673" }, "action_statement": "Vulnerability CVE-2026-25673 affects version 5.0.2.post5+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-28T19:09:04.720419+00:00", "status_notes": "Vulnerability CVE-2026-25674 affects version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2026-25674" }, "action_statement": "Vulnerability CVE-2026-25674 affects version 5.0.2.post5+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-28T19:07:12.211534+00:00", "status_notes": "Vulnerability CVE-2026-33033 affects version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2026-33033" }, "action_statement": "Vulnerability CVE-2026-33033 affects version 5.0.2.post5+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-28T19:05:19.418788+00:00", "status_notes": "Vulnerability CVE-2026-33034 affects version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2026-33034" }, "action_statement": "Vulnerability CVE-2026-33034 affects version 5.0.2.post5+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-28T19:09:04.720419+00:00", "status_notes": "Vulnerability CVE-2026-3902 affects version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2026-3902" }, "action_statement": "Vulnerability CVE-2026-3902 affects version 5.0.2.post5+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-28T19:08:06.540752+00:00", "status_notes": "Vulnerability CVE-2026-4277 affects version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2026-4277" }, "action_statement": "Vulnerability CVE-2026-4277 affects version 5.0.2.post5+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-10-28T19:07:12.211534+00:00", "status_notes": "Vulnerability CVE-2026-4292 affects version 5.0.2.post5+tuxcare of django.", "vulnerability": { "name": "CVE-2026-4292" }, "action_statement": "Vulnerability CVE-2026-4292 affects version 5.0.2.post5+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-48587 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post6+tuxcare.", "vulnerability": { "name": "CVE-2026-48587" }, "action_statement": "Vulnerability CVE-2026-48587 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post6+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-48588 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post6+tuxcare.", "vulnerability": { "name": "CVE-2026-48588" }, "action_statement": "Vulnerability CVE-2026-48588 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post6+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-53877 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post6+tuxcare.", "vulnerability": { "name": "CVE-2026-53877" }, "action_statement": "Vulnerability CVE-2026-53877 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post6+tuxcare." }, { "status": "not_affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-53878 does not affect version 5.0.2.post5+tuxcare of django. not_affected \u2014 Django 5.0.2 is not affected by CVE-2026-53878. The vulnerable code (DomainNameValidator class) does not exist in this version - it was introduced in Django 5.1. Django 5.0.2 uses _simple_domain_name_validator which already validates against newlines via string.whitespace.", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2026-53878" }, "impact_statement": "not_affected \u2014 Django 5.0.2 is not affected by CVE-2026-53878. The vulnerable code (DomainNameValidator class) does not exist in this version - it was introduced in Django 5.1. Django 5.0.2 uses _simple_domain_name_validator which already validates against newlines via string.whitespace." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-6873 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post6+tuxcare.", "vulnerability": { "name": "CVE-2026-6873" }, "action_statement": "Vulnerability CVE-2026-6873 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post6+tuxcare." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.0.2.post5+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.0.2.post5+tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-8404 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post6+tuxcare.", "vulnerability": { "name": "CVE-2026-8404" }, "action_statement": "Vulnerability CVE-2026-8404 affects version 5.0.2.post5+tuxcare of django, and is fixed in 5.0.2.post6+tuxcare." } ] }