{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:cde16170-c2a8-50b6-8c77-7c375bf923ac", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "django", "purl": "pkg:pypi/django@5.0.post19+tuxcare", "type": "library", "bom-ref": "pkg:pypi/django@5.0.post19+tuxcare", "version": "5.0.post19+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.post19+tuxcare" } ], "bom-ref": "urn:uuid:00fb94ec-97e6-51ce-831f-acab1e77d075", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-45115 affects version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2021-45116", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:03d7765c-32a7-5789-a1a1-99fdec4b9361", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-45116 affects version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2021-45452", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:5c9bf045-da57-5d9a-a9cc-d1af1609cd91", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2021-45452 does not affect version 5.0.post19+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.post19+tuxcare" } ], "bom-ref": "urn:uuid:f75880d1-195d-5681-b64d-bf71cc6c9396", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2022-22818 does not affect version 5.0.post19+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.post19+tuxcare" } ], "bom-ref": "urn:uuid:b417adc9-1e8b-584f-b006-5a9c6cc0d4bf", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-23833 affects version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2022-28346", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:0c2cef80-bf61-580d-97e9-a5c5bbb25910", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-28346 affects version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2022-28347", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:e5ffae2c-766d-5429-8d4b-b9ef687c9284", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-28347 affects version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2022-34265", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:d24beb9f-e8c5-55d9-84f1-a347281eea2f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-34265 affects version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2022-36359", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:fcbf092d-fc1b-5833-ad2e-3abf6066aff9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-36359 affects version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2022-41323", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:5fc945f3-65d9-518f-a298-c3dc70871ace", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-41323 affects version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2023-23969", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:8c2c76c6-bab8-59c1-9958-49b3f42216fb", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-23969 affects version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2023-24580", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:711f113e-2d8e-5d51-8b9f-1e6f71422fef", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-24580 affects version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2023-31047", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:bec13534-08f1-5475-9e80-aec221b449b9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-31047 affects version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2023-36053", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:fa2ec551-cfb6-5333-9a20-568699eca27a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-36053 affects version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2023-41164", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:0e0cb88a-d840-5ba8-8e0b-374784cee8d8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-41164 affects version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2023-43665", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:29e0e59a-01c8-5673-8102-3fb6d14319cf", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-43665 affects version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2023-46695", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:1d279719-bea7-5a06-9805-04877aea03b1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-46695 affects version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2024-24680", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:704e600c-b52e-507d-a72b-9c07f2fe2e9b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-24680 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2024-27351", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:271e26ea-6520-51df-a724-88eabeb5a285", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-27351 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2024-38875", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:7264ad41-bc6b-5e9e-bbc0-c80fedc703de", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-38875 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2024-39329", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:9bd4b859-7253-587e-92b9-fc433fe54f7d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39329 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2024-39330", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:87a35ca0-00da-597a-b8c0-b39c27dbc3be", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39330 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2024-39614", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:b3a15feb-93f0-5024-98e7-2932db507952", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39614 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2024-41989", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:9cd4585b-7f73-53d7-8b0a-72b2dfbd547d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-41989 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2024-41990", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:51314af3-b517-58e5-83d4-2cf2be9541a1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-41990 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2024-41991", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:8ad42332-eb18-5fbf-a077-f07a621335fc", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-41991 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2024-42005", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:2f123341-2cb5-50e5-b422-d6f162b1baf0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-42005 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2024-45230", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:bf099696-fc31-56e3-913d-d170cd6d34ac", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-45230 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2024-45231", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:6c85019a-7f16-5e4e-9e96-526a419f7dd1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-45231 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2024-53907", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:8486b16e-dad6-5c1d-94a1-96f8b6dfe442", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-53907 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2024-53908", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:e6726c90-b2da-59c6-9a97-987f8ab826c0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-53908 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2024-56374", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:3dadfd5a-4a2c-570d-9c84-b033eb9da88a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-56374 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2025-13372", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:51635038-d0e5-5308-b1fe-2a648609b350", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13372 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2025-13473", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:af304f24-6cc5-5840-ad94-cb0e69a1d19b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13473 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2025-14550", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:9f6d097e-0d09-5a1d-8182-7d234d981122", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-14550 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2025-26699", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:f14a5edd-3c68-5f5b-aae8-8b31d8237de4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-26699 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2025-27556", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:57dbf418-07b3-5774-a0bd-5bb09cf81e63", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-27556 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2025-32873", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:2f3f6fb6-7ee2-51a1-9cee-05a384642000", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-32873 affects version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2025-48432", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:ef865912-50f9-5a02-8f35-3e10fbd87736", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-48432 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2025-57833", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:2d321ee2-fc3d-54d4-be2f-deac68bc8c4f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-57833 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2025-59681", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:9bb743aa-c9c7-5793-88c0-f1dfbcba614c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-59681 affects version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2025-59682", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:88bd9946-8d2f-5d45-847c-a4258700d712", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-59682 affects version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2025-64458", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:a9f5a673-9500-5c71-80ee-728080cc7e3d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64458 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2025-64459", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:ef6d3ee1-6cd7-53bc-87a2-980e76fe7987", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64459 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2025-64460", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:8ff843d6-aad7-5e1b-9bff-0ac77aabdf57", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64460 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2026-1207", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:e9c57f9a-c7a3-5031-9ffb-066d7b949dd2", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1207 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2026-1285", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:387734fe-a263-561e-af96-49ed7b60b389", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1285 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2026-1287", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:65f0a95e-206d-5d15-a253-38ca6dfecebc", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1287 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2026-1312", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:cb6c9b19-7b58-5be6-9cb4-139eba8738db", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1312 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2026-15307", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:8e1e7c2f-af7e-56e3-bf87-9e6493dad8d1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15307 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2026-15830", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:39ea483d-3a1f-5e84-bdd5-f7b342f642fb", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15830 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2026-25673", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:e3d5b243-13df-5c40-bbd6-29ac88fb8e40", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-25673 affects version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2026-25674", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:b6761fe1-0bc7-57e4-b2e5-15ebb37d1876", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-25674 affects version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2026-33033", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:a0dff74f-af1b-552f-8f54-bcf5c3d5309e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33033 affects version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2026-33034", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:07b38232-5d93-5e43-935a-9ada67311885", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33034 affects version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2026-3902", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:373fbc3c-6a63-5086-966a-366ce454bb4d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-3902 affects version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2026-4277", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:59b72777-df76-5ec8-a782-2bb43a87be96", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-4277 affects version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2026-4292", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:0532b93f-b7f6-536d-a37f-e4e57ea64cf8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-4292 affects version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2026-48587", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:3b74da79-4b66-58f8-b6ee-12f24ad607c8", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48587 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2026-48588", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:122cebf1-81de-54a4-9ac5-44ee2d2dffb3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48588 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2026-53877", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:285ea963-c424-5959-8730-d6f4b842210a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-53877 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2026-53878", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:45686b5f-4fe5-5f19-85cd-ca5819769b15", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-53878 does not affect version 5.0.post19+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.post19+tuxcare" } ], "bom-ref": "urn:uuid:962e4e49-9c94-5ae8-9f28-02fee2cd912b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-6873 is fixed in version 5.0.post19+tuxcare of django." } }, { "id": "CVE-2026-8404", "affects": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ], "bom-ref": "urn:uuid:a3ba6d4d-df2a-518f-aa50-d18c7839e6d5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-8404 is fixed in version 5.0.post19+tuxcare of django." } } ], "dependencies": [ { "ref": "pkg:pypi/django@5.0.post19+tuxcare" } ] }