{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:bd02c864-91cd-5184-b54a-476c3dfeff84", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "django", "purl": "pkg:pypi/django@5.0.post16+tuxcare", "type": "library", "bom-ref": "pkg:pypi/django@5.0.post16+tuxcare", "version": "5.0.post16+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.post16+tuxcare" } ], "bom-ref": "urn:uuid:1ea4abe4-cd0c-57c4-ab2a-d1462a496249", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-45115 affects version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2021-45116", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:72755ead-80e6-5b61-bd3e-b2c58c5faf3a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-45116 affects version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2021-45452", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:f0174ab8-e140-5873-a628-415c4162f03f", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2021-45452 does not affect version 5.0.post16+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.post16+tuxcare" } ], "bom-ref": "urn:uuid:332d3f88-8e60-502f-a14b-fa46603a034b", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2022-22818 does not affect version 5.0.post16+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.post16+tuxcare" } ], "bom-ref": "urn:uuid:1a715b21-0275-57eb-b849-8c0770197d61", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-23833 affects version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2022-28346", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:c21df288-064f-552d-adbe-27a09f9d8f25", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-28346 affects version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2022-28347", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:1a328727-b957-59f5-9cd1-05af46110a0f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-28347 affects version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2022-34265", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:ee0f5e1b-93b7-5b14-a1f6-d2119e9daabc", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-34265 affects version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2022-36359", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:fc7fb8b8-572e-5c59-9f3d-27556f5b83e2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-36359 affects version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2022-41323", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:99127e6f-0e89-5824-97fb-16b2f99b4ae8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-41323 affects version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2023-23969", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:701c9a62-24cb-541e-a101-e88c5f78ff87", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-23969 affects version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2023-24580", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:416ae4c8-1137-5d28-838e-b3a89dfe7a3f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-24580 affects version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2023-31047", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:37361b9b-399f-5f01-8fdf-8b2cdea6eb7b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-31047 affects version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2023-36053", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:62df019a-828b-5f08-9fa3-55eb08f7d652", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-36053 affects version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2023-41164", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:c2ed035e-f085-5111-8a2c-dd193794a9df", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-41164 affects version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2023-43665", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:f46229e4-f92e-5cda-9874-f389c59db542", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-43665 affects version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2023-46695", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:7c72dd64-ebc8-5076-ba9f-101d9dfa9c9f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-46695 affects version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2024-24680", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:9584aa42-37db-54f6-9d9d-0766bd9b837d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-24680 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2024-27351", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:8898b441-fdd6-5c78-b77a-caa5e89ad52b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-27351 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2024-38875", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:bc82fc38-8d91-5949-aad3-002f14bb7cda", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-38875 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2024-39329", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:5a41fb48-d764-55ee-83d3-e83fd99e4a89", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39329 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2024-39330", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:1b540c2e-adfb-5478-b0ee-a4a27b17af12", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39330 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2024-39614", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:9631f996-19a9-5c0c-8926-cf8a4b0fd972", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39614 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2024-41989", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:3d9275cb-2f5d-591e-9bb4-67b287c2f512", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-41989 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2024-41990", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:4228e76d-3de3-5e63-b786-f4942c25ad69", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-41990 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2024-41991", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:7385ef1d-9242-52bd-bf4e-fd3a24fa7ee2", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-41991 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2024-42005", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:9e531ff3-d8c1-5483-8a09-2c4f4359396a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-42005 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2024-45230", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:5185df5b-c95b-5157-8e1b-a12f4dc3845f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-45230 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2024-45231", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:15de8ffe-0065-5744-975c-25041839d58a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-45231 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2024-53907", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:fb7fb1fe-c3bf-5a5d-be7d-544a5875fc5b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-53907 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2024-53908", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:b8ae16ff-9a6e-5761-be0d-2553829760cd", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-53908 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2024-56374", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:dc3d65d2-4984-5c78-9f0d-3e49f209e2d8", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-56374 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2025-13372", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:f6240b89-79ba-5d90-ae0e-c5c463876c9f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-13372 affects version 5.0.post16+tuxcare of django, and is fixed in 5.0.post17+tuxcare." } }, { "id": "CVE-2025-13473", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:be6c7ab1-b82e-5daf-bca6-c5930960bb45", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13473 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2025-14550", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:fea8e69e-572e-537e-bcdb-00f38d861c58", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-14550 affects version 5.0.post16+tuxcare of django, and is fixed in 5.0.post17+tuxcare." } }, { "id": "CVE-2025-26699", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:5e40d208-9144-5ad6-87f1-430e50a139f4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-26699 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2025-27556", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:86396557-33e1-5fff-ad6b-2bcb76bd8155", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-27556 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2025-32873", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:fc513cf9-5b54-58d4-91bd-7db226df52eb", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-32873 affects version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2025-48432", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:b0c222a9-9d0d-589d-bc84-272b700ef0e6", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-48432 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2025-57833", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:177600e6-09a6-52c5-8197-137ec162af3b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-57833 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2025-59681", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:dab22881-ec90-5251-be35-d8942fa7fd3a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-59681 affects version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2025-59682", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:ebce3dc5-4c27-5966-8fe0-335e09b895ff", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-59682 affects version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2025-64458", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:44f3fb3e-08a5-510d-a00c-840c5ad8ab1d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64458 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2025-64459", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:e089f890-8688-56b4-b030-367c4877de6f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64459 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2025-64460", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:7a9914fa-a2c6-5ac3-8639-e2af59627ceb", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64460 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2026-1207", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:3a44ac15-e60b-5bc0-aa2d-64bc3a335410", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1207 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2026-1285", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:5b1e7eff-5502-54e6-a382-3331560d3991", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-1285 affects version 5.0.post16+tuxcare of django, and is fixed in 5.0.post17+tuxcare." } }, { "id": "CVE-2026-1287", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:32f95cb5-ec0f-5749-9529-b23c6e93b73a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1287 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2026-1312", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:ffe8083f-8db9-5546-bffc-6aed8fe81c8b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1312 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2026-15307", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:e3647b77-c4a2-58e3-989e-9f7e3bc755e7", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15307 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2026-15830", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:6063ef3c-2b79-5aed-867a-27916c0fbe24", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15830 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2026-25673", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:be41e298-e733-52cb-8d09-41d0dc25d471", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-25673 affects version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2026-25674", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:a7b46306-6a4b-528b-9b19-d8d89c8fff8e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-25674 affects version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2026-33033", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:96a7e5b3-f994-5b04-8290-d5be70bced37", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33033 affects version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2026-33034", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:e0352ee2-ca3e-597c-84a1-af96eb23ca30", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33034 affects version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2026-3902", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:d3e60f84-0f95-5989-97f8-04140e8e2e93", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-3902 affects version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2026-4277", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:93cd00e5-5988-5aed-a1c3-561dfd83006c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-4277 affects version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2026-4292", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:858b5378-78e0-53aa-b488-37959b635b96", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-4292 affects version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2026-48587", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:8661f8fc-6d99-54c7-8154-799fa2e512bb", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48587 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2026-48588", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:da0a71b9-fc4c-5ba0-924f-c88c57eecba5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48588 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2026-53877", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:1f420f26-2bba-5641-abc1-97582cdf489f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-53877 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2026-53878", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:e08f1fd6-6ef5-5e34-a58c-0c5108af782c", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-53878 does not affect version 5.0.post16+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.post16+tuxcare" } ], "bom-ref": "urn:uuid:3e9a8532-a779-5685-a252-303bce20d6cf", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-6873 is fixed in version 5.0.post16+tuxcare of django." } }, { "id": "CVE-2026-8404", "affects": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ], "bom-ref": "urn:uuid:ad2ffe70-201f-5d97-8fb8-25edaf8b3b54", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-8404 is fixed in version 5.0.post16+tuxcare of django." } } ], "dependencies": [ { "ref": "pkg:pypi/django@5.0.post16+tuxcare" } ] }