{ "@id": "urn:uuid:e5adf46b-4004-4ce8-8608-73982bf326cf", "role": "Document Creator", "author": "https://tuxcare.com", "version": 9, "@context": "https://openvex.dev/ns/v0.2.0", "timestamp": "2026-10-29T19:58:08.504070+00:00", "statements": [ { "status": "affected", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-28T19:05:19.418788+00:00", "status_notes": "Vulnerability CVE-2021-45115 affects version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2021-45115" }, "action_statement": "Vulnerability CVE-2021-45115 affects version 4.2.post17+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-28T19:05:19.418788+00:00", "status_notes": "Vulnerability CVE-2021-45116 affects version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2021-45116" }, "action_statement": "Vulnerability CVE-2021-45116 affects version 4.2.post17+tuxcare of django." }, { "status": "not_affected", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-29T19:13:00.100912+00:00", "status_notes": "Vulnerability CVE-2021-45452 does not affect version 4.2.post17+tuxcare of django. not_affected \u2014 Django 4.2.0 is not affected by CVE-2021-45452. The vulnerability was fixed in the upstream Django release before version 4.2.0 was published. All security defenses from the patch (backslash normalization, path traversal detection, post-save validation, and relative path enforcement) are present in the target codebase. The fix was authored by upstream Django maintainers and shipped in the base ...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2021-45452" }, "impact_statement": "not_affected \u2014 Django 4.2.0 is not affected by CVE-2021-45452. The vulnerability was fixed in the upstream Django release before version 4.2.0 was published. All security defenses from the patch (backslash normalization, path traversal detection, post-save validation, and relative path enforcement) are present in the target codebase. The fix was authored by upstream Django maintainers and shipped in the base ..." }, { "status": "not_affected", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-29T19:58:08.504070+00:00", "status_notes": "Vulnerability CVE-2022-22818 does not affect version 4.2.post17+tuxcare of django. not_affected \u2014 Django 4.2 is not affected by CVE-2022-22818. The vulnerability in the `{% debug %}` template tag (unescaped output leading to XSS) was fixed in upstream Django before the 4.2 release. The fix commit 394517f07886495efcf79f95c7ee402a9437bd68 by Markus Holtermann is present in HEAD and predates all TuxCare work on this branch. The target code properly escapes all pformat() output and includes a D...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2022-22818" }, "impact_statement": "not_affected \u2014 Django 4.2 is not affected by CVE-2022-22818. The vulnerability in the `{% debug %}` template tag (unescaped output leading to XSS) was fixed in upstream Django before the 4.2 release. The fix commit 394517f07886495efcf79f95c7ee402a9437bd68 by Markus Holtermann is present in HEAD and predates all TuxCare work on this branch. The target code properly escapes all pformat() output and includes a D..." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-28T19:07:12.211534+00:00", "status_notes": "Vulnerability CVE-2022-23833 affects version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2022-23833" }, "action_statement": "Vulnerability CVE-2022-23833 affects version 4.2.post17+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-28T19:06:21.253116+00:00", "status_notes": "Vulnerability CVE-2022-28346 affects version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2022-28346" }, "action_statement": "Vulnerability CVE-2022-28346 affects version 4.2.post17+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-28T19:07:12.211534+00:00", "status_notes": "Vulnerability CVE-2022-28347 affects version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2022-28347" }, "action_statement": "Vulnerability CVE-2022-28347 affects version 4.2.post17+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-28T19:08:06.540752+00:00", "status_notes": "Vulnerability CVE-2022-34265 affects version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2022-34265" }, "action_statement": "Vulnerability CVE-2022-34265 affects version 4.2.post17+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-28T19:08:06.540752+00:00", "status_notes": "Vulnerability CVE-2022-36359 affects version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2022-36359" }, "action_statement": "Vulnerability CVE-2022-36359 affects version 4.2.post17+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-28T19:07:12.211534+00:00", "status_notes": "Vulnerability CVE-2022-41323 affects version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2022-41323" }, "action_statement": "Vulnerability CVE-2022-41323 affects version 4.2.post17+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-28T19:08:06.540752+00:00", "status_notes": "Vulnerability CVE-2023-23969 affects version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2023-23969" }, "action_statement": "Vulnerability CVE-2023-23969 affects version 4.2.post17+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-28T19:05:19.418788+00:00", "status_notes": "Vulnerability CVE-2023-24580 affects version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2023-24580" }, "action_statement": "Vulnerability CVE-2023-24580 affects version 4.2.post17+tuxcare of django." }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:59:00.113234+00:00", "status_notes": "Vulnerability CVE-2023-31047 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2023-31047" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:59:00.113234+00:00", "status_notes": "Vulnerability CVE-2023-36053 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2023-36053" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:59:00.113234+00:00", "status_notes": "Vulnerability CVE-2023-41164 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2023-41164" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:59:00.113234+00:00", "status_notes": "Vulnerability CVE-2023-43665 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2023-43665" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:59:00.113234+00:00", "status_notes": "Vulnerability CVE-2023-46695 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2023-46695" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:59:00.113234+00:00", "status_notes": "Vulnerability CVE-2024-24680 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2024-24680" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:59:00.113234+00:00", "status_notes": "Vulnerability CVE-2024-27351 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2024-27351" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:59:00.113234+00:00", "status_notes": "Vulnerability CVE-2024-38875 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2024-38875" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:59:00.113234+00:00", "status_notes": "Vulnerability CVE-2024-39329 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2024-39329" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:59:00.113234+00:00", "status_notes": "Vulnerability CVE-2024-39330 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2024-39330" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:59:00.113234+00:00", "status_notes": "Vulnerability CVE-2024-39614 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2024-39614" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:59:00.113234+00:00", "status_notes": "Vulnerability CVE-2024-41989 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2024-41989" } }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T08:08:00.236952+00:00", "status_notes": "Vulnerability CVE-2024-41990 affects version 4.2.post17+tuxcare of django, and is fixed in 4.2.post18+tuxcare.", "vulnerability": { "name": "CVE-2024-41990" }, "action_statement": "Vulnerability CVE-2024-41990 affects version 4.2.post17+tuxcare of django, and is fixed in 4.2.post18+tuxcare." }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:59:00.113234+00:00", "status_notes": "Vulnerability CVE-2024-41991 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2024-41991" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:59:00.113234+00:00", "status_notes": "Vulnerability CVE-2024-42005 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2024-42005" } }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T08:08:00.236952+00:00", "status_notes": "Vulnerability CVE-2024-45230 affects version 4.2.post17+tuxcare of django, and is fixed in 4.2.post18+tuxcare.", "vulnerability": { "name": "CVE-2024-45230" }, "action_statement": "Vulnerability CVE-2024-45230 affects version 4.2.post17+tuxcare of django, and is fixed in 4.2.post18+tuxcare." }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:59:00.113234+00:00", "status_notes": "Vulnerability CVE-2024-45231 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2024-45231" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:59:00.113234+00:00", "status_notes": "Vulnerability CVE-2024-53907 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2024-53907" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:59:00.113234+00:00", "status_notes": "Vulnerability CVE-2024-53908 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2024-53908" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:59:00.113234+00:00", "status_notes": "Vulnerability CVE-2024-56374 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2024-56374" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:58:00.201033+00:00", "status_notes": "Vulnerability CVE-2025-13372 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2025-13372" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:58:00.201033+00:00", "status_notes": "Vulnerability CVE-2025-13473 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2025-13473" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:58:00.201033+00:00", "status_notes": "Vulnerability CVE-2025-14550 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2025-14550" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:59:00.113234+00:00", "status_notes": "Vulnerability CVE-2025-26699 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2025-26699" } }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-28T19:06:21.253116+00:00", "status_notes": "Vulnerability CVE-2025-27556 affects version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2025-27556" }, "action_statement": "Vulnerability CVE-2025-27556 affects version 4.2.post17+tuxcare of django." }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:59:00.113234+00:00", "status_notes": "Vulnerability CVE-2025-32873 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2025-32873" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:58:00.201033+00:00", "status_notes": "Vulnerability CVE-2025-48432 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2025-48432" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:58:00.201033+00:00", "status_notes": "Vulnerability CVE-2025-57833 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2025-57833" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:58:00.201033+00:00", "status_notes": "Vulnerability CVE-2025-59681 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2025-59681" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:58:00.201033+00:00", "status_notes": "Vulnerability CVE-2025-59682 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2025-59682" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:58:00.201033+00:00", "status_notes": "Vulnerability CVE-2025-64458 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2025-64458" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:58:00.201033+00:00", "status_notes": "Vulnerability CVE-2025-64459 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2025-64459" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:58:00.201033+00:00", "status_notes": "Vulnerability CVE-2025-64460 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2025-64460" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:58:00.201033+00:00", "status_notes": "Vulnerability CVE-2026-1207 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2026-1207" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:58:00.201033+00:00", "status_notes": "Vulnerability CVE-2026-1285 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2026-1285" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:58:00.201033+00:00", "status_notes": "Vulnerability CVE-2026-1287 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2026-1287" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:58:00.201033+00:00", "status_notes": "Vulnerability CVE-2026-1312 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2026-1312" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:58:00.201033+00:00", "status_notes": "Vulnerability CVE-2026-15307 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2026-15307" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:58:00.201033+00:00", "status_notes": "Vulnerability CVE-2026-15830 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2026-15830" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:58:00.201033+00:00", "status_notes": "Vulnerability CVE-2026-25673 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2026-25673" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:58:00.201033+00:00", "status_notes": "Vulnerability CVE-2026-25674 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2026-25674" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:58:00.201033+00:00", "status_notes": "Vulnerability CVE-2026-33033 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2026-33033" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:58:00.201033+00:00", "status_notes": "Vulnerability CVE-2026-33034 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2026-33034" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:58:00.201033+00:00", "status_notes": "Vulnerability CVE-2026-3902 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2026-3902" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:58:00.201033+00:00", "status_notes": "Vulnerability CVE-2026-4277 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2026-4277" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:58:00.201033+00:00", "status_notes": "Vulnerability CVE-2026-4292 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2026-4292" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:58:00.201033+00:00", "status_notes": "Vulnerability CVE-2026-48587 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2026-48587" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:58:00.201033+00:00", "status_notes": "Vulnerability CVE-2026-48588 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2026-48588" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:58:00.201033+00:00", "status_notes": "Vulnerability CVE-2026-53877 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2026-53877" } }, { "status": "not_affected", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:58:00.201033+00:00", "status_notes": "Vulnerability CVE-2026-53878 does not affect version 4.2.post17+tuxcare of django. not_affected \u2014 Django 4.2.0 is not affected by CVE-2026-53878. The vulnerable component `DomainNameValidator` does not exist in this version (it was introduced in Django 5.1). All existing domain validation mechanisms in Django 4.2.0 already prohibit newlines: URLValidator explicitly checks for newlines in `unsafe_chars`, EmailValidator uses regex that doesn't match newlines, and _simple_domain_name_validator...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2026-53878" }, "impact_statement": "not_affected \u2014 Django 4.2.0 is not affected by CVE-2026-53878. The vulnerable component `DomainNameValidator` does not exist in this version (it was introduced in Django 5.1). All existing domain validation mechanisms in Django 4.2.0 already prohibit newlines: URLValidator explicitly checks for newlines in `unsafe_chars`, EmailValidator uses regex that doesn't match newlines, and _simple_domain_name_validator..." }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:58:00.201033+00:00", "status_notes": "Vulnerability CVE-2026-6873 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2026-6873" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@4.2.post17+tuxcare", "identifiers": { "purl": "pkg:pypi/django@4.2.post17+tuxcare" } } ], "timestamp": "2026-10-19T06:58:00.201033+00:00", "status_notes": "Vulnerability CVE-2026-8404 is fixed in version 4.2.post17+tuxcare of django.", "vulnerability": { "name": "CVE-2026-8404" } } ] }