{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:b974b109-c3f5-5fdd-9019-7b4f515186f2", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "django", "purl": "pkg:pypi/django@5.0.post20+tuxcare", "type": "library", "bom-ref": "pkg:pypi/django@5.0.post20+tuxcare", "version": "5.0.post20+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.post20+tuxcare" } ], "bom-ref": "urn:uuid:4923d933-4a5b-560a-8cf0-4e3b7bf736ff", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-45115 affects version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2021-45116", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:87d8ab7a-50f2-5681-ad50-e32192f367b0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-45116 affects version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2021-45452", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:000efe13-5f91-5dff-9584-0e0ee016dde0", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2021-45452 does not affect version 5.0.post20+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.post20+tuxcare" } ], "bom-ref": "urn:uuid:55e5257b-816d-56d3-bd7e-8840afdff098", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2022-22818 does not affect version 5.0.post20+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.post20+tuxcare" } ], "bom-ref": "urn:uuid:b9309ffb-7bd5-5e83-aab0-4cb4bff1a95d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-23833 affects version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2022-28346", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:affac9ad-346c-5a87-8784-1d2072d0ec9d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-28346 affects version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2022-28347", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:8e243264-6b81-55e2-863d-00bffe17134d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-28347 affects version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2022-34265", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:a15bb702-2292-5f61-8b08-6740640154ce", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-34265 affects version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2022-36359", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:d54d75e0-f4e4-55d8-8223-977751cc24ee", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-36359 affects version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2022-41323", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:e4c1aeef-8cb0-587a-ad5a-c70da8f0282b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-41323 affects version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2023-23969", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:76de0b72-74fe-5dd1-9289-c369ca4d5117", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-23969 affects version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2023-24580", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:f055f6a1-7729-5caa-b5c7-99097946de83", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-24580 affects version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2023-31047", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:6078aaff-3bc9-51e6-9308-b257943a43ed", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-31047 affects version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2023-36053", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:afc531a5-7303-562c-8c7e-e101a9618bc2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-36053 affects version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2023-41164", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:5e322891-1b19-56ae-85f2-b3775a385ea9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-41164 affects version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2023-43665", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:10cdb04e-92f1-5ddf-9107-2f9218a06399", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-43665 affects version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2023-46695", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:512afa22-79b7-5fb0-b134-4577a46bb391", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-46695 affects version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2024-24680", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:e61ccae5-353f-5ce8-87ba-ac11343415f9", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-24680 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2024-27351", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:fe623763-3ce5-5283-b2a5-34ea6af29a43", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-27351 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2024-38875", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:2fd9176a-ec33-5edf-bcfd-fc5ca4aadde0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-38875 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2024-39329", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:aee2d1a8-20a1-5bf1-bc69-e2e6fb3abfe3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39329 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2024-39330", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:efaa673d-1c95-555d-a540-5008c2d9a91c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39330 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2024-39614", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:0e4362f0-5241-543d-af0d-dbf49eeabfd4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39614 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2024-41989", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:8f71575b-5615-5afe-a3a7-739bcc7b617c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-41989 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2024-41990", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:7844f9cf-8ce9-5223-8a29-f3f1ccb4d32a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-41990 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2024-41991", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:fbd9dc26-3477-5258-80f4-e48db1f67014", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-41991 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2024-42005", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:a58268a7-9495-5833-ac21-0f2871af96d3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-42005 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2024-45230", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:45194f19-891f-580b-bfb3-809c7aa9e4b6", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-45230 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2024-45231", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:367420f1-d5f5-525a-a34b-df8c57160815", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-45231 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2024-53907", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:e9a67428-b28b-5580-a6d2-05a24c9590e8", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-53907 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2024-53908", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:545c99cb-fdd8-51d9-b865-d548fd771860", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-53908 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2024-56374", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:777b4343-3de6-5865-9101-76c58b796d85", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-56374 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2025-13372", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:bf4ce3b0-2c19-5d0d-977c-37e1007f4cd9", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13372 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2025-13473", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:5e322469-4125-563c-ac6b-e4c9c6999561", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13473 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2025-14550", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:81093718-e9ff-5f5d-9b6a-5d2fe0e2bf52", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-14550 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2025-26699", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:c8ae0ef1-4f30-53ea-a58d-cade75835ee5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-26699 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2025-27556", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:fe157765-b0ea-533f-adec-22f7070265d6", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-27556 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2025-32873", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:be0bfb99-6f78-5cfb-8033-433d428310c6", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-32873 affects version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2025-48432", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:3b951360-004d-528e-9c99-bf5de2f63fa1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-48432 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2025-57833", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:32301a9e-e4bf-5cd8-9953-8ee44a4e1e5a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-57833 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2025-59681", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:82f768b0-b5a4-5857-8297-53717e344028", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-59681 affects version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2025-59682", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:0424984e-9553-577b-aab7-a2fb9ca7cf11", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-59682 affects version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2025-64458", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:a5738553-7574-5f4e-b0b4-26360def4c2b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64458 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2025-64459", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:8661dc56-8d7c-51f4-a7c9-ba9db8bcf233", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64459 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2025-64460", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:c50c0ce3-f64b-5131-b2d3-a4117f6fbc4c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64460 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2026-1207", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:0b63b2e7-b1f0-5d30-bfde-de61a2b2053a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1207 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2026-1285", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:ffbb09b7-ed08-5aaa-81c3-2a7b9b5404fd", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1285 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2026-1287", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:4d8701c6-a99c-551e-8ea5-f4b648a015e3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1287 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2026-1312", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:d494bff5-da86-5225-8648-76effbb851b9", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1312 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2026-15307", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:f7b3e6d0-4457-5405-a05d-41fe3d1fd321", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15307 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2026-15830", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:f4429150-fde1-5c9f-b176-d0ead391bdd2", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15830 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2026-25673", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:bd9f68e1-eefc-5695-8483-f05d86dd857b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-25673 affects version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2026-25674", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:52337242-4101-5661-a4af-735eecc18917", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-25674 affects version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2026-33033", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:f952e29a-c161-50d2-bf65-0a8d6a97bbae", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33033 affects version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2026-33034", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:d836bd26-258f-5fae-b5ff-cfad4ee68999", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33034 affects version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2026-3902", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:e92030a9-eba1-56a7-8c5d-c51f3a18e5ee", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-3902 affects version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2026-4277", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:f70afc0f-9da4-5c62-90c0-f648e01f7e21", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-4277 affects version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2026-4292", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:37486839-fbd8-5ee1-88f7-ac578e99faee", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-4292 affects version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2026-48587", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:af52c4e2-f596-59df-bb2e-35fd76fa03ad", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48587 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2026-48588", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:5ef16fd4-f83a-59eb-a2ff-3135ef366dd4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48588 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2026-53877", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:50583139-ff54-5b96-9cea-afc97c240e29", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-53877 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2026-53878", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:ca392ee2-abab-5a6d-938a-6c837fc25527", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-53878 does not affect version 5.0.post20+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.post20+tuxcare" } ], "bom-ref": "urn:uuid:0fb06693-1c39-5896-affe-e670920e1248", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-6873 is fixed in version 5.0.post20+tuxcare of django." } }, { "id": "CVE-2026-8404", "affects": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ], "bom-ref": "urn:uuid:43ce952d-502e-58fd-ba7a-c9015bcf1f5f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-8404 is fixed in version 5.0.post20+tuxcare of django." } } ], "dependencies": [ { "ref": "pkg:pypi/django@5.0.post20+tuxcare" } ] }