{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:28a05a48-76f6-5008-a9bf-324e2a668e33", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "django", "purl": "pkg:pypi/django@5.0.post14+tuxcare", "type": "library", "bom-ref": "pkg:pypi/django@5.0.post14+tuxcare", "version": "5.0.post14+tuxcare", "pedigree": { "ancestors": [ { "name": "django", "purl": "pkg:pypi/django@5.0", "type": "library", "version": "5.0" } ] }, "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2021-45115", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:e70fe6c3-9522-5f59-b3e1-6cd5aae46dd0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-45115 affects version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2021-45116", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:2f24cb4a-b8a8-5cda-bacb-cdaee40a4e5c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-45116 affects version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2021-45452", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:fd4cab6c-a347-503d-b446-4e0821539e00", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2021-45452 does not affect version 5.0.post14+tuxcare of django. not_affected \u2014 CVE-2021-45452 (directory traversal in Storage.save()) is NOT present in Django 5.0.0.post20+tuxcare. The upstream fix (commit 6d343d01c5 by Florian Apolloner) shipped in Django 5.0.0 and predates all TuxCare commits in this branch. All defense mechanisms are present: backslash normalization (base.py:75,116), path traversal detection (base.py:77-80,119-122), relative path enforcement (filesyste...", "justification": "code_not_present" } }, { "id": "CVE-2022-22818", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:505725ed-36e0-5977-818e-301d4293b66c", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2022-22818 does not affect version 5.0.post14+tuxcare of django. not_affected \u2014 The target Django 5.0 repository is NOT AFFECTED by CVE-2022-22818. The vulnerability (XSS via unescaped output in the {% debug %} template tag) was fixed by Django upstream in commit 394517f078 on 2022-01-02, three years before this Django 5.0 release. The fix\u2014which wraps pformat() output with HTML entity encoding via escape() and blocks output when DEBUG=False\u2014is present at django/template/de...", "justification": "code_not_present" } }, { "id": "CVE-2022-23833", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:8bb39824-a10d-5e32-a586-23f493f7187c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-23833 affects version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2022-28346", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:a23ee6da-bb0d-5b90-9f09-c3997c07cee5", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-28346 affects version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2022-28347", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:8e325150-2cb1-5483-988c-9ccd5d0b83cc", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-28347 affects version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2022-34265", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:b582dbb8-c159-57a6-a18d-9a5816b6986f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-34265 affects version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2022-36359", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:77fba044-4f55-5e21-8866-b4c7d37da42a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-36359 affects version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2022-41323", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:959bd869-ab8b-5a25-a62c-23a586d2d78a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-41323 affects version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2023-23969", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:5abab0c3-064d-5990-9e5d-1fe6d4f1715c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-23969 affects version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2023-24580", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:4d45319d-54fc-5c03-b341-9a455f6a1d76", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-24580 affects version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2023-31047", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:b0c4ba17-1c1f-576f-8535-745c0bc1f5cb", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-31047 affects version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2023-36053", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:5d4db0c0-0543-5520-bce9-a482d301dbed", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-36053 affects version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2023-41164", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:4fad3664-5565-5c71-b09a-8d967b27b7d9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-41164 affects version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2023-43665", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:f2fda30a-19f5-5295-a9e6-d3886bf5e95d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-43665 affects version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2023-46695", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:34bf1429-841c-5985-8c9f-afa9f54a0f06", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-46695 affects version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2024-24680", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:14182ed9-f000-54e5-bba7-0c534925255e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-24680 is fixed in version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2024-27351", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:43c55daf-c82b-56eb-9825-5ea3e7c78f35", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-27351 is fixed in version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2024-38875", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:9159827c-b6ea-5564-bc4a-3937a58ec289", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-38875 is fixed in version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2024-39329", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:129ca083-8231-525c-b4e1-c7589fd9899f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39329 is fixed in version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2024-39330", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:2244ef49-187a-56ce-89a3-7ac72d5f06dc", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39330 is fixed in version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2024-39614", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:6a27cf17-c09e-5963-89ec-d097e4fade1d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39614 is fixed in version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2024-41989", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:df116bc3-f431-5d4b-854a-801f34ab37b8", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-41989 is fixed in version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2024-41990", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:116b3921-ec63-5abd-b409-cd6d5b632bf5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-41990 is fixed in version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2024-41991", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:cf2d579e-2063-55ee-8cb0-112b4ed2b3c4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-41991 is fixed in version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2024-42005", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:4e2339e5-2265-5c5d-aa74-236a0bd7e566", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-42005 is fixed in version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2024-45230", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:57b9b94f-787f-5c66-a355-2d61ecfec338", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-45230 affects version 5.0.post14+tuxcare of django, and is fixed in 5.0.post15+tuxcare." } }, { "id": "CVE-2024-45231", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:e7d0a17e-effb-5449-9d79-6703cf74df32", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-45231 is fixed in version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2024-53907", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:a827d6ef-2b0b-576c-8fe3-4e863955409c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-53907 is fixed in version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2024-53908", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:1a78e84d-c5b1-5dee-ab44-7f6ca7f5d5ff", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-53908 is fixed in version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2024-56374", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:9de592a1-bebe-5e89-8bbe-e838d87da04e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-56374 is fixed in version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2025-13372", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:4a92ce6b-de08-5761-b5ce-9bdf8aa0a89b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-13372 affects version 5.0.post14+tuxcare of django, and is fixed in 5.0.post17+tuxcare." } }, { "id": "CVE-2025-13473", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:475a9fff-6d51-5da9-9686-d8d2abfe2eb4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13473 is fixed in version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2025-14550", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:bc3bc8d7-9b22-5a8b-8211-058a084ba701", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-14550 affects version 5.0.post14+tuxcare of django, and is fixed in 5.0.post17+tuxcare." } }, { "id": "CVE-2025-26699", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:dc2ff037-34a0-5b14-8e7e-9329172e6828", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-26699 is fixed in version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2025-27556", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:66987c1e-40bc-5c2b-bbc0-49adadd24a48", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-27556 is fixed in version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2025-32873", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:682b83f7-35b0-5b68-9ec2-794e439b919c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-32873 affects version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2025-48432", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:9fccbd60-8966-552b-9eaf-7ae8be983c42", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-48432 is fixed in version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2025-57833", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:e5c6ffa1-fa46-5f36-a9af-529887283cb9", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-57833 is fixed in version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2025-59681", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:b03cd4cd-72c9-5bd3-913b-869c6356d84b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-59681 affects version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2025-59682", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:c11c0b4c-1b90-5636-bc48-129dee9a361e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-59682 affects version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2025-64458", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:0940bbb9-008f-56e7-acd9-a88de85bf57a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64458 is fixed in version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2025-64459", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:d02e6d59-65b9-596e-82c1-cbec08661290", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64459 is fixed in version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2025-64460", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:3803b6d3-ee15-57e9-a94a-2854e19ecfac", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64460 is fixed in version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2026-1207", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:a95ee693-2a13-57cf-bcc6-efa9943c9f28", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1207 is fixed in version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2026-1285", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:6967c064-6a51-50c7-be09-19d0e99afae9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-1285 affects version 5.0.post14+tuxcare of django, and is fixed in 5.0.post17+tuxcare." } }, { "id": "CVE-2026-1287", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:642bbf46-ff8e-56c5-96e7-191ecfeb8c80", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1287 is fixed in version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2026-1312", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:78b55375-3973-5ca0-8721-9c87df023fe7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-1312 affects version 5.0.post14+tuxcare of django, and is fixed in 5.0.post15+tuxcare." } }, { "id": "CVE-2026-15307", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:6c6c5e22-1599-5983-be17-d99719a360da", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-15307 affects version 5.0.post14+tuxcare of django, and is fixed in 5.0.post16+tuxcare." } }, { "id": "CVE-2026-15830", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:b58753ef-eec8-5efd-98b9-38341f204525", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-15830 affects version 5.0.post14+tuxcare of django, and is fixed in 5.0.post16+tuxcare." } }, { "id": "CVE-2026-25673", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:6345e152-9a83-54b8-a1b6-0a6dd2904fc7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-25673 affects version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2026-25674", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:c128df07-28cf-5c91-9878-34052aabfdc1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-25674 affects version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2026-33033", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:673269de-8fd0-55fe-b921-9b259a9d646a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33033 affects version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2026-33034", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:d8ef8de4-b5d3-5d86-930d-ea76a7fcdcb0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33034 affects version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2026-3902", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:a6c41728-2f20-5bb0-844a-2dace62da63c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-3902 affects version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2026-4277", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:8e327e37-95e3-5b19-885d-c25456be1231", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-4277 affects version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2026-4292", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:4c6dd127-4b50-53ba-8839-429c1bd6b131", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-4292 affects version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2026-48587", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:8175275c-c1bd-5857-8e57-d683b38976bd", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48587 is fixed in version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2026-48588", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:a08514e5-b10d-5c94-ab56-4c3eb2724880", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48588 is fixed in version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2026-53877", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:e487ffce-80e5-5d70-9ed0-14f769b1ca40", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-53877 is fixed in version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2026-53878", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:a068b9c1-128c-5cba-9c96-0112648c4819", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-53878 does not affect version 5.0.post14+tuxcare of django. not_affected \u2014 Django 5.0 does not contain the vulnerable DomainNameValidator class. This validator was introduced in Django 5.1 (commit 4971a9afe5). Since the specific component affected by CVE-2026-53878 does not exist in this version, Django 5.0 cannot be affected by this vulnerability. Additionally, all domain validators present in Django 5.0 (_simple_domain_name_validator, EmailValidator, URLValidator) a...", "justification": "code_not_present" } }, { "id": "CVE-2026-6873", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:8ebffaeb-6e89-5e4a-91fe-2fa6243fa8dd", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-6873 is fixed in version 5.0.post14+tuxcare of django." } }, { "id": "CVE-2026-8404", "affects": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ], "bom-ref": "urn:uuid:ffe61d3c-9fc7-5f1c-8302-ff091a275395", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-8404 is fixed in version 5.0.post14+tuxcare of django." } } ], "dependencies": [ { "ref": "pkg:pypi/django@5.0.post14+tuxcare" } ] }