{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:d96878ca-668a-5e48-b8c7-1586da8cc282", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "django", "purl": "pkg:pypi/django@5.0.post18+tuxcare", "type": "library", "bom-ref": "pkg:pypi/django@5.0.post18+tuxcare", "version": "5.0.post18+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.post18+tuxcare" } ], "bom-ref": "urn:uuid:8ffbdc83-a1a9-5644-8f67-34d2e4549533", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-45115 affects version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2021-45116", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:f5a4fbb1-1322-5275-8862-43437db8aa00", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-45116 affects version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2021-45452", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:2fc4e6ad-f590-543c-9abf-23b8d191639e", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2021-45452 does not affect version 5.0.post18+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.post18+tuxcare" } ], "bom-ref": "urn:uuid:6aaffefa-bf02-569e-a2e9-8c006d6c2e94", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2022-22818 does not affect version 5.0.post18+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.post18+tuxcare" } ], "bom-ref": "urn:uuid:6875d205-f37e-556c-b8c8-40c6027a2820", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-23833 affects version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2022-28346", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:6c8f65c1-a3d6-5cf5-ab21-9654e0f372e4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-28346 affects version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2022-28347", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:b2635d81-967c-56fd-b8b1-298f6bbabe70", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-28347 affects version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2022-34265", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:efa0b14b-f101-54a2-93c4-181aeda9dc1a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-34265 affects version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2022-36359", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:c879bd29-37f1-5a80-aee3-452c5fc8781d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-36359 affects version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2022-41323", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:7a57cb83-a70b-5814-ae2c-a2909d5620d2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-41323 affects version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2023-23969", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:5438ad3a-c5e5-514b-8d15-27c9ce5fdd19", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-23969 affects version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2023-24580", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:0cbeaf59-b61f-5f28-9493-46b7b42b12dc", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-24580 affects version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2023-31047", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:49de528a-e40a-598a-82f4-1aaa5c343fe2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-31047 affects version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2023-36053", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:f9cbba8a-38e3-5bea-b386-960ae61efb45", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-36053 affects version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2023-41164", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:645b1dd8-428a-56c1-8052-2f9eb6a31be8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-41164 affects version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2023-43665", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:b94f254a-ccc3-5150-90c0-d0e857258d06", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-43665 affects version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2023-46695", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:3f0dd96e-3f1c-51e8-9fb6-ab8af045eb3b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-46695 affects version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2024-24680", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:8c24ab48-96c0-5a01-b3b5-eac22d65e058", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-24680 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2024-27351", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:16e510e3-3ed7-57c0-ae5d-cc1dc3e1e0d8", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-27351 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2024-38875", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:af3006a3-0015-51e3-b1d6-d229166e8a28", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-38875 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2024-39329", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:9637a637-a5fc-5b27-b7e6-a1a285372890", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39329 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2024-39330", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:72dc7900-70c8-5a63-821f-1ac7d9672250", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39330 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2024-39614", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:8d49590f-b08d-5cd5-a24b-574641a0f7f2", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39614 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2024-41989", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:bc0a3dcb-f270-54b5-b6fb-727b3c680748", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-41989 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2024-41990", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:f4143c22-73c4-56ae-a4f3-aad36e51867e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-41990 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2024-41991", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:98ad1980-6e6c-51d3-acc2-a50fb5ad39ac", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-41991 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2024-42005", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:860bf28b-a0c8-5256-b9cd-ffc2d22fe049", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-42005 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2024-45230", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:602cb8c6-8c42-5bf6-9836-b6350d1e8fbf", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-45230 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2024-45231", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:1dbd9286-3823-5bc3-94e9-1c24ab548a8e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-45231 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2024-53907", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:c74372d5-f0e5-545a-af6e-3e9202c7ad79", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-53907 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2024-53908", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:a6374fed-1169-5748-bdca-c8b3e946039c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-53908 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2024-56374", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:335b98f9-cceb-50e8-998d-0400ff9336ef", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-56374 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2025-13372", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:9c27e2d0-94f8-53b7-b736-a42603f2be75", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13372 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2025-13473", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:f4472620-e872-539b-80ac-59d4d7822329", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13473 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2025-14550", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:de8e172e-51d5-5cb0-a00a-331d9269f711", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-14550 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2025-26699", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:47b0035b-e44b-5da3-9c53-848bc3cd7698", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-26699 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2025-27556", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:87fecd15-f305-5dff-817d-8253893bece4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-27556 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2025-32873", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:0f2f1f9b-074a-5b2a-8a05-5846d00290cc", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-32873 affects version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2025-48432", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:3d8ec386-d117-5605-a727-c82e86cfd401", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-48432 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2025-57833", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:90e62566-771b-5939-b028-105ec5c2a335", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-57833 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2025-59681", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:3084713b-2c7e-5095-b839-ecac47b42190", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-59681 affects version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2025-59682", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:36af4156-8c3b-56d4-84c1-f2e0414c4023", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-59682 affects version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2025-64458", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:716b315b-54dc-5619-a4fc-1b99e7b5a287", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64458 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2025-64459", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:3aca85dd-d870-5006-a254-8894d0cf591b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64459 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2025-64460", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:5826b763-a1ab-5930-aa7d-bc502085113c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64460 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2026-1207", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:40f87314-b903-5b5d-a5f9-8bcd39dc0a34", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1207 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2026-1285", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:1d047d9e-ce1d-53b3-a0a0-ca1dd954b088", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1285 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2026-1287", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:a9c8d1f8-06ac-5720-9ae2-5703b424a084", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1287 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2026-1312", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:0d6f2934-b473-51ab-9876-9ab28767b45c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1312 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2026-15307", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:927f464a-9f41-51a4-8ad8-6b61b1f31da3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15307 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2026-15830", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:5d08af86-e7a1-5580-92cc-4a847b468de9", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15830 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2026-25673", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:a7c359f4-135a-583b-80a0-6863b14a535e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-25673 affects version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2026-25674", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:396b940a-6455-59a4-ba75-fe19e919ec81", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-25674 affects version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2026-33033", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:3b3fa7b8-eba1-5ef1-85fc-5fadabd8faca", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33033 affects version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2026-33034", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:80aec0a7-5d12-5468-8cb0-25567409f012", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33034 affects version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2026-3902", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:c4a50005-e900-5b39-bd39-efb6cb84d0f2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-3902 affects version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2026-4277", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:fca2da5a-b21b-585b-bb87-2471f14913fe", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-4277 affects version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2026-4292", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:5633499f-8efd-57fb-a97e-07599344eedb", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-4292 affects version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2026-48587", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:54285df7-8de1-5ed2-b733-a4739ce8c905", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48587 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2026-48588", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:3754059b-9f5e-53d7-9b3a-d81a10acbe6f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48588 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2026-53877", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:f7671c60-0ec4-55cc-898f-eefc6c0c996d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-53877 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2026-53878", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:42291781-fd4a-5c4e-b641-7acc72a72996", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-53878 does not affect version 5.0.post18+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.post18+tuxcare" } ], "bom-ref": "urn:uuid:214581ef-2547-5332-bc9e-229ba0fef005", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-6873 is fixed in version 5.0.post18+tuxcare of django." } }, { "id": "CVE-2026-8404", "affects": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ], "bom-ref": "urn:uuid:182daf45-7367-5b2b-9d45-03688a5c6400", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-8404 is fixed in version 5.0.post18+tuxcare of django." } } ], "dependencies": [ { "ref": "pkg:pypi/django@5.0.post18+tuxcare" } ] }