{ "@id": "urn:uuid:67a88efc-5642-4d15-ad95-be6ac88a1095", "role": "Document Creator", "author": "https://tuxcare.com", "version": 13, "@context": "https://openvex.dev/ns/v0.2.0", "timestamp": "2026-10-29T20:46:09.941779+00:00", "statements": [ { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:05:19.418788+00:00", "status_notes": "Vulnerability CVE-2021-45115 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2021-45115" }, "action_statement": "Vulnerability CVE-2021-45115 affects version 5.1.4.post9+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:05:19.418788+00:00", "status_notes": "Vulnerability CVE-2021-45116 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2021-45116" }, "action_statement": "Vulnerability CVE-2021-45116 affects version 5.1.4.post9+tuxcare of django." }, { "status": "not_affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-29T19:07:59.324773+00:00", "status_notes": "Vulnerability CVE-2021-45452 does not affect version 5.1.4.post9+tuxcare of django. not_affected \u2014 Django 5.1.4.post10+tuxcare is not affected by CVE-2021-45452. The directory traversal vulnerability in Storage.save() was fixed in upstream Django commit 6d343d01c5 (Dec 2021) by Florian Apolloner, which was already present in the Django 5.1.4 upstream release before TuxCare's maintenance began. All protection mechanisms from the fix are present and active in the target: path normalization, \"....", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2021-45452" }, "impact_statement": "not_affected \u2014 Django 5.1.4.post10+tuxcare is not affected by CVE-2021-45452. The directory traversal vulnerability in Storage.save() was fixed in upstream Django commit 6d343d01c5 (Dec 2021) by Florian Apolloner, which was already present in the Django 5.1.4 upstream release before TuxCare's maintenance began. All protection mechanisms from the fix are present and active in the target: path normalization, \"...." }, { "status": "not_affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-29T19:55:14.707436+00:00", "status_notes": "Vulnerability CVE-2022-22818 does not affect version 5.1.4.post9+tuxcare of django. not_affected \u2014 Django 5.1.4 is not affected by CVE-2022-22818. The vulnerability (XSS via unescaped output in {% debug %} template tag) was fixed in Django 4.0.2, 3.2.12, and 2.2.27. The target version 5.1.4 already contains the upstream fix from commit 394517f078 by Markus Holtermann, which was shipped in the upstream release before TuxCare's onboarding. The DebugNode.render() method properly HTML-encodes al...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2022-22818" }, "impact_statement": "not_affected \u2014 Django 5.1.4 is not affected by CVE-2022-22818. The vulnerability (XSS via unescaped output in {% debug %} template tag) was fixed in Django 4.0.2, 3.2.12, and 2.2.27. The target version 5.1.4 already contains the upstream fix from commit 394517f078 by Markus Holtermann, which was shipped in the upstream release before TuxCare's onboarding. The DebugNode.render() method properly HTML-encodes al..." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:07:12.211534+00:00", "status_notes": "Vulnerability CVE-2022-23833 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2022-23833" }, "action_statement": "Vulnerability CVE-2022-23833 affects version 5.1.4.post9+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:06:21.253116+00:00", "status_notes": "Vulnerability CVE-2022-28346 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2022-28346" }, "action_statement": "Vulnerability CVE-2022-28346 affects version 5.1.4.post9+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:06:21.253116+00:00", "status_notes": "Vulnerability CVE-2022-28347 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2022-28347" }, "action_statement": "Vulnerability CVE-2022-28347 affects version 5.1.4.post9+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:08:06.540752+00:00", "status_notes": "Vulnerability CVE-2022-34265 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2022-34265" }, "action_statement": "Vulnerability CVE-2022-34265 affects version 5.1.4.post9+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:08:06.540752+00:00", "status_notes": "Vulnerability CVE-2022-36359 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2022-36359" }, "action_statement": "Vulnerability CVE-2022-36359 affects version 5.1.4.post9+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:07:12.211534+00:00", "status_notes": "Vulnerability CVE-2022-41323 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2022-41323" }, "action_statement": "Vulnerability CVE-2022-41323 affects version 5.1.4.post9+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:08:06.540752+00:00", "status_notes": "Vulnerability CVE-2023-23969 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2023-23969" }, "action_statement": "Vulnerability CVE-2023-23969 affects version 5.1.4.post9+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:05:19.418788+00:00", "status_notes": "Vulnerability CVE-2023-24580 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2023-24580" }, "action_statement": "Vulnerability CVE-2023-24580 affects version 5.1.4.post9+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:07:12.211534+00:00", "status_notes": "Vulnerability CVE-2023-31047 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2023-31047" }, "action_statement": "Vulnerability CVE-2023-31047 affects version 5.1.4.post9+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:06:21.253116+00:00", "status_notes": "Vulnerability CVE-2023-36053 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2023-36053" }, "action_statement": "Vulnerability CVE-2023-36053 affects version 5.1.4.post9+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:23:04.118629+00:00", "status_notes": "Vulnerability CVE-2023-41164 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2023-41164" }, "action_statement": "Vulnerability CVE-2023-41164 affects version 5.1.4.post9+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:23:04.118629+00:00", "status_notes": "Vulnerability CVE-2023-43665 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2023-43665" }, "action_statement": "Vulnerability CVE-2023-43665 affects version 5.1.4.post9+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:23:04.118629+00:00", "status_notes": "Vulnerability CVE-2023-46695 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2023-46695" }, "action_statement": "Vulnerability CVE-2023-46695 affects version 5.1.4.post9+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:09:04.720419+00:00", "status_notes": "Vulnerability CVE-2024-24680 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2024-24680" }, "action_statement": "Vulnerability CVE-2024-24680 affects version 5.1.4.post9+tuxcare of django." }, { "status": "not_affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-29T20:18:06.334068+00:00", "status_notes": "Vulnerability CVE-2024-27351 does not affect version 5.1.4.post9+tuxcare of django. not_affected \u2014 Django 5.1.4 is not affected by CVE-2024-27351. The vulnerable regex pattern `r\"<[^>]+?>|([^<>\\s]+)\"` used in `Truncator.words()` was removed in January 2023 (commit 6ee37ada32) when Django switched to HTMLParser-based truncation. Django 5.1 branched from main after this architectural change, so 5.1.4 never contained the vulnerable code. The CVE only affected older branches (3.2, 4.2, 5.0) that...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2024-27351" }, "impact_statement": "not_affected \u2014 Django 5.1.4 is not affected by CVE-2024-27351. The vulnerable regex pattern `r\"<[^>]+?>|([^<>\\s]+)\"` used in `Truncator.words()` was removed in January 2023 (commit 6ee37ada32) when Django switched to HTMLParser-based truncation. Django 5.1 branched from main after this architectural change, so 5.1.4 never contained the vulnerable code. The CVE only affected older branches (3.2, 4.2, 5.0) that..." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:05:19.418788+00:00", "status_notes": "Vulnerability CVE-2024-38875 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2024-38875" }, "action_statement": "Vulnerability CVE-2024-38875 affects version 5.1.4.post9+tuxcare of django." }, { "status": "not_affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-29T19:13:00.100912+00:00", "status_notes": "Vulnerability CVE-2024-39329 does not affect version 5.1.4.post9+tuxcare of django. not_affected \u2014 CVE-2024-39329 timing attack vulnerability is NOT present in Django 5.1.4. The fix (commit f5d16483f3) was already included in the upstream Django 5.1.4 release before TuxCare began maintaining this version. The vulnerable code pattern has been replaced with timing-normalized code that calls make_password() to equalize response times for unusable passwords.", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2024-39329" }, "impact_statement": "not_affected \u2014 CVE-2024-39329 timing attack vulnerability is NOT present in Django 5.1.4. The fix (commit f5d16483f3) was already included in the upstream Django 5.1.4 release before TuxCare began maintaining this version. The vulnerable code pattern has been replaced with timing-normalized code that calls make_password() to equalize response times for unusable passwords." }, { "status": "not_affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-29T20:46:09.941779+00:00", "status_notes": "Vulnerability CVE-2024-39330 does not affect version 5.1.4.post9+tuxcare of django. not_affected \u2014 CVE-2024-39330 is not present in Django 5.1.4. The upstream fix (commit 6d36203648) that adds three validate_file_name() calls in Storage.save() and backslash normalization in validate_file_name() was already included in the Django 5.1.4 release before TuxCare onboarded it. The vulnerable pattern (missing path traversal validation allowing directory traversal via \"..\" or absolute paths) is not ...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2024-39330" }, "impact_statement": "not_affected \u2014 CVE-2024-39330 is not present in Django 5.1.4. The upstream fix (commit 6d36203648) that adds three validate_file_name() calls in Storage.save() and backslash normalization in validate_file_name() was already included in the Django 5.1.4 release before TuxCare onboarded it. The vulnerable pattern (missing path traversal validation allowing directory traversal via \"..\" or absolute paths) is not ..." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:07:12.211534+00:00", "status_notes": "Vulnerability CVE-2024-39614 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2024-39614" }, "action_statement": "Vulnerability CVE-2024-39614 affects version 5.1.4.post9+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:07:12.211534+00:00", "status_notes": "Vulnerability CVE-2024-41989 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2024-41989" }, "action_statement": "Vulnerability CVE-2024-41989 affects version 5.1.4.post9+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:05:19.418788+00:00", "status_notes": "Vulnerability CVE-2024-41990 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2024-41990" }, "action_statement": "Vulnerability CVE-2024-41990 affects version 5.1.4.post9+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:08:06.540752+00:00", "status_notes": "Vulnerability CVE-2024-41991 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2024-41991" }, "action_statement": "Vulnerability CVE-2024-41991 affects version 5.1.4.post9+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:05:19.418788+00:00", "status_notes": "Vulnerability CVE-2024-42005 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2024-42005" }, "action_statement": "Vulnerability CVE-2024-42005 affects version 5.1.4.post9+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:05:19.418788+00:00", "status_notes": "Vulnerability CVE-2024-45230 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2024-45230" }, "action_statement": "Vulnerability CVE-2024-45230 affects version 5.1.4.post9+tuxcare of django." }, { "status": "not_affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-29T18:43:56.275811+00:00", "status_notes": "Vulnerability CVE-2024-45231 does not affect version 5.1.4.post9+tuxcare of django. not_affected \u2014 CVE-2024-45231 is NOT present in Django 5.1.4. The vulnerability allowed email enumeration when password reset email sending failed, causing observable 500 errors. The upstream Django fix (commit 3c733c78d6 by Natalia) wraps email_message.send() in a try-except block that catches and logs exceptions instead of propagating them. This fix was already present in the Django 5.1.4 upstream release b...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2024-45231" }, "impact_statement": "not_affected \u2014 CVE-2024-45231 is NOT present in Django 5.1.4. The vulnerability allowed email enumeration when password reset email sending failed, causing observable 500 errors. The upstream Django fix (commit 3c733c78d6 by Natalia) wraps email_message.send() in a try-except block that catches and logs exceptions instead of propagating them. This fix was already present in the Django 5.1.4 upstream release b..." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:08:06.540752+00:00", "status_notes": "Vulnerability CVE-2024-53907 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2024-53907" }, "action_statement": "Vulnerability CVE-2024-53907 affects version 5.1.4.post9+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:08:06.540752+00:00", "status_notes": "Vulnerability CVE-2024-53908 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2024-53908" }, "action_statement": "Vulnerability CVE-2024-53908 affects version 5.1.4.post9+tuxcare of django." }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-08T10:14:00.068840+00:00", "status_notes": "Vulnerability CVE-2024-56374 is fixed in version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2024-56374" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-08T10:14:00.068840+00:00", "status_notes": "Vulnerability CVE-2025-13372 is fixed in version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2025-13372" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-08T10:14:00.068840+00:00", "status_notes": "Vulnerability CVE-2025-13473 is fixed in version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2025-13473" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-08T10:14:00.068840+00:00", "status_notes": "Vulnerability CVE-2025-14550 is fixed in version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2025-14550" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-08T10:14:00.068840+00:00", "status_notes": "Vulnerability CVE-2025-26699 is fixed in version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2025-26699" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-08T10:14:00.068840+00:00", "status_notes": "Vulnerability CVE-2025-27556 is fixed in version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2025-27556" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-08T10:14:00.068840+00:00", "status_notes": "Vulnerability CVE-2025-32873 is fixed in version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2025-32873" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-08T10:14:00.068840+00:00", "status_notes": "Vulnerability CVE-2025-48432 is fixed in version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2025-48432" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-08T10:14:00.068840+00:00", "status_notes": "Vulnerability CVE-2025-57833 is fixed in version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2025-57833" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-08T10:14:00.068840+00:00", "status_notes": "Vulnerability CVE-2025-59681 is fixed in version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2025-59681" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-08T10:14:00.068840+00:00", "status_notes": "Vulnerability CVE-2025-59682 is fixed in version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2025-59682" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-08T10:14:00.068840+00:00", "status_notes": "Vulnerability CVE-2025-64458 is fixed in version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2025-64458" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-08T10:14:00.068840+00:00", "status_notes": "Vulnerability CVE-2025-64459 is fixed in version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2025-64459" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-08T10:14:00.068840+00:00", "status_notes": "Vulnerability CVE-2025-64460 is fixed in version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2025-64460" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-08T10:14:00.068840+00:00", "status_notes": "Vulnerability CVE-2026-1207 is fixed in version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2026-1207" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-08T10:14:00.068840+00:00", "status_notes": "Vulnerability CVE-2026-1285 is fixed in version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2026-1285" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-08T10:14:00.068840+00:00", "status_notes": "Vulnerability CVE-2026-1287 is fixed in version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2026-1287" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-08T10:14:00.068840+00:00", "status_notes": "Vulnerability CVE-2026-1312 is fixed in version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2026-1312" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-08T10:14:00.068840+00:00", "status_notes": "Vulnerability CVE-2026-15307 is fixed in version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2026-15307" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-08T10:14:00.068840+00:00", "status_notes": "Vulnerability CVE-2026-15830 is fixed in version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2026-15830" } }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:06:21.253116+00:00", "status_notes": "Vulnerability CVE-2026-25673 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2026-25673" }, "action_statement": "Vulnerability CVE-2026-25673 affects version 5.1.4.post9+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:09:04.720419+00:00", "status_notes": "Vulnerability CVE-2026-25674 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2026-25674" }, "action_statement": "Vulnerability CVE-2026-25674 affects version 5.1.4.post9+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:07:12.211534+00:00", "status_notes": "Vulnerability CVE-2026-33033 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2026-33033" }, "action_statement": "Vulnerability CVE-2026-33033 affects version 5.1.4.post9+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:05:19.418788+00:00", "status_notes": "Vulnerability CVE-2026-33034 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2026-33034" }, "action_statement": "Vulnerability CVE-2026-33034 affects version 5.1.4.post9+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:09:04.720419+00:00", "status_notes": "Vulnerability CVE-2026-3902 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2026-3902" }, "action_statement": "Vulnerability CVE-2026-3902 affects version 5.1.4.post9+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:08:06.540752+00:00", "status_notes": "Vulnerability CVE-2026-4277 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2026-4277" }, "action_statement": "Vulnerability CVE-2026-4277 affects version 5.1.4.post9+tuxcare of django." }, { "status": "affected", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-28T19:07:12.211534+00:00", "status_notes": "Vulnerability CVE-2026-4292 affects version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2026-4292" }, "action_statement": "Vulnerability CVE-2026-4292 affects version 5.1.4.post9+tuxcare of django." }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-08T10:14:00.068840+00:00", "status_notes": "Vulnerability CVE-2026-48587 is fixed in version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2026-48587" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-08T10:14:00.068840+00:00", "status_notes": "Vulnerability CVE-2026-48588 is fixed in version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2026-48588" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-08T10:14:00.068840+00:00", "status_notes": "Vulnerability CVE-2026-53877 is fixed in version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2026-53877" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-08T10:14:00.068840+00:00", "status_notes": "Vulnerability CVE-2026-53878 is fixed in version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2026-53878" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-08T10:14:00.068840+00:00", "status_notes": "Vulnerability CVE-2026-6873 is fixed in version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2026-6873" } }, { "status": "fixed", "products": [ { "@id": "pkg:pypi/django@5.1.4.post9+tuxcare", "identifiers": { "purl": "pkg:pypi/django@5.1.4.post9+tuxcare" } } ], "timestamp": "2026-10-08T10:14:00.068840+00:00", "status_notes": "Vulnerability CVE-2026-8404 is fixed in version 5.1.4.post9+tuxcare of django.", "vulnerability": { "name": "CVE-2026-8404" } } ] }