{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:c1c9f57a-fd71-5e39-9014-41b10bbb4254", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "django", "purl": "pkg:pypi/django@4.2.post15+tuxcare", "type": "library", "bom-ref": "pkg:pypi/django@4.2.post15+tuxcare", "version": "4.2.post15+tuxcare", "pedigree": { "ancestors": [ { "name": "django", "purl": "pkg:pypi/django@4.2", "type": "library", "version": "4.2" } ] }, "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2023-31047", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:614b7a54-4784-56d6-b92a-0410c2564e28", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-31047 affects version 4.2.post15+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2023-36053", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:d953d657-b4ea-5f8b-88aa-0a4c0a1fa068", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-36053 affects version 4.2.post15+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2023-41164", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:937886a0-8a9c-53f1-b812-1a52bb5ce3a3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-41164 affects version 4.2.post15+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2023-43665", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:959f88f4-3b6f-56b9-b636-ca9cf4dbbb4b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-43665 affects version 4.2.post15+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2023-46695", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:9b3b7604-cc62-5706-9461-24cc371f09cf", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-46695 affects version 4.2.post15+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-24680", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:1a49ade4-6d69-506e-8639-01ee609d557d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-24680 affects version 4.2.post15+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-27351", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:dd8b0a22-d933-54b4-b04d-f291f0cf01ce", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-27351 affects version 4.2.post15+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-38875", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:46bd0837-62f5-58b5-b755-6fa8f8989a08", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-38875 affects version 4.2.post15+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-39329", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:b4a1b271-c227-5172-a8b2-4360748120a3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-39329 affects version 4.2.post15+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-39330", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:540f3005-19e2-572d-ab48-a990a860a264", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-39330 affects version 4.2.post15+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-39614", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:5500a204-8fe2-5128-841b-ea529a232367", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-39614 affects version 4.2.post15+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-41989", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:91487ca9-f81d-55ca-a6e1-b2786ada2ff6", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-41989 affects version 4.2.post15+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-41990", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:e8708454-1fee-579d-82a6-bd84d7565717", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-41990 affects version 4.2.post15+tuxcare of django, and is fixed in 4.2.post18+tuxcare." } }, { "id": "CVE-2024-41991", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:1529a49c-8a29-56f4-bc2b-d2d812a29c11", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-41991 affects version 4.2.post15+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-42005", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:a9ac43ec-9e30-5c1f-8dc1-90bc73ccb0f8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-42005 affects version 4.2.post15+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-45230", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:2170ef31-7750-5a05-82e6-8223d1fba25b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-45230 affects version 4.2.post15+tuxcare of django, and is fixed in 4.2.post18+tuxcare." } }, { "id": "CVE-2024-45231", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:abd04a0d-950f-5e54-96ca-8235aaf54a1e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-45231 affects version 4.2.post15+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-53907", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:a74d9edb-62ea-5c7e-9ad5-e1529d7ec373", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-53907 affects version 4.2.post15+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-53908", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:648e961c-d066-5d95-8ea6-de3e7bb24144", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-53908 affects version 4.2.post15+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-56374", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:0e0ac417-75af-522b-bb70-48c7d1695c1e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-56374 affects version 4.2.post15+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2025-13372", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:c51b469e-d351-5da2-a6c8-ca43d3edbac3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13372 is fixed in version 4.2.post15+tuxcare of django." } }, { "id": "CVE-2025-13473", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:26f5c9f0-d5ef-548e-919f-f2b599005a9b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13473 is fixed in version 4.2.post15+tuxcare of django." } }, { "id": "CVE-2025-14550", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:993fd641-4bbb-5e0d-95e6-bf70d259ea80", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-14550 is fixed in version 4.2.post15+tuxcare of django." } }, { "id": "CVE-2025-26699", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:e9a26425-2e00-5a5d-a848-11494986c5c9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-26699 affects version 4.2.post15+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2025-32873", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:a4abd5e5-7b46-514a-81bc-27e550058d41", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-32873 affects version 4.2.post15+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2025-48432", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:9292ba50-3e01-5cb4-b8ac-3941a2afab53", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-48432 is fixed in version 4.2.post15+tuxcare of django." } }, { "id": "CVE-2025-57833", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:78b440f5-ee51-5321-8788-882d305d2361", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-57833 is fixed in version 4.2.post15+tuxcare of django." } }, { "id": "CVE-2025-59681", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:583845e4-a8e6-55a7-aa9e-a450e70625c1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-59681 is fixed in version 4.2.post15+tuxcare of django." } }, { "id": "CVE-2025-59682", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:13174bed-761a-5999-b9c2-eb969176b042", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-59682 is fixed in version 4.2.post15+tuxcare of django." } }, { "id": "CVE-2025-64458", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:3698c249-8d89-5795-bbce-f63e174a1434", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64458 is fixed in version 4.2.post15+tuxcare of django." } }, { "id": "CVE-2025-64459", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:08002f58-1952-51ec-984a-2c5d45116034", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64459 is fixed in version 4.2.post15+tuxcare of django." } }, { "id": "CVE-2025-64460", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:f2f1e47e-9f9d-5e75-b18e-ca4703bdbac0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64460 is fixed in version 4.2.post15+tuxcare of django." } }, { "id": "CVE-2026-1207", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:917b7603-3439-524f-a6f3-af5bc1b71dd0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1207 is fixed in version 4.2.post15+tuxcare of django." } }, { "id": "CVE-2026-1285", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:ddf3a2c8-45c8-520b-9ac2-b7ac067d75f2", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1285 is fixed in version 4.2.post15+tuxcare of django." } }, { "id": "CVE-2026-1287", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:27fb8d0e-b022-5db4-929b-5222e99c1afc", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1287 is fixed in version 4.2.post15+tuxcare of django." } }, { "id": "CVE-2026-1312", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:be07d2dc-f72e-5a1f-8e79-b686890d7b21", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1312 is fixed in version 4.2.post15+tuxcare of django." } }, { "id": "CVE-2026-15307", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:d72c2dbb-effe-5b5a-a540-ee2693ba41dd", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15307 is fixed in version 4.2.post15+tuxcare of django." } }, { "id": "CVE-2026-15830", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:eeda6ad8-4422-5ca9-b048-41ae18e0afa4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15830 is fixed in version 4.2.post15+tuxcare of django." } }, { "id": "CVE-2026-25673", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:065c4eef-26e6-5c32-9343-cfcc339ed7f1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-25673 is fixed in version 4.2.post15+tuxcare of django." } }, { "id": "CVE-2026-25674", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:ce1177b0-7bf2-5314-a8a7-615989db031c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-25674 is fixed in version 4.2.post15+tuxcare of django." } }, { "id": "CVE-2026-33033", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:02470a90-c5f0-55b3-be8e-a91c2a347562", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-33033 is fixed in version 4.2.post15+tuxcare of django." } }, { "id": "CVE-2026-33034", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:5f834efb-7ad4-5f06-84b8-7c38dfbb1c5e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-33034 is fixed in version 4.2.post15+tuxcare of django." } }, { "id": "CVE-2026-3902", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:feb5f7ff-8b31-5e9c-b650-1b42b42eeda7", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-3902 is fixed in version 4.2.post15+tuxcare of django." } }, { "id": "CVE-2026-4277", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:d7db2543-faca-5813-8e5c-0d1476e7d314", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-4277 is fixed in version 4.2.post15+tuxcare of django." } }, { "id": "CVE-2026-4292", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:1c5763c2-7c00-5172-972d-24a69798a2ea", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-4292 is fixed in version 4.2.post15+tuxcare of django." } }, { "id": "CVE-2026-48587", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:0068153b-6641-503e-92f8-b1d78155343d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48587 is fixed in version 4.2.post15+tuxcare of django." } }, { "id": "CVE-2026-48588", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:b6d8ee0d-e6c4-5739-9535-77c1c4e10e39", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48588 is fixed in version 4.2.post15+tuxcare of django." } }, { "id": "CVE-2026-53877", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:eb9286fc-46ad-5811-b159-0c9a6439d349", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-53877 is fixed in version 4.2.post15+tuxcare of django." } }, { "id": "CVE-2026-53878", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:06612d0b-5721-57b5-8419-35a7deb30073", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-53878 does not affect version 4.2.post15+tuxcare of django. not_affected \u2014 Django 4.2.0 is not affected by CVE-2026-53878. The vulnerable component `DomainNameValidator` does not exist in this version (it was introduced in Django 5.1). All existing domain validation mechanisms in Django 4.2.0 already prohibit newlines: URLValidator explicitly checks for newlines in `unsafe_chars`, EmailValidator uses regex that doesn't match newlines, and _simple_domain_name_validator...", "justification": "code_not_present" } }, { "id": "CVE-2026-6873", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:59ac2f51-78a9-5507-9424-6ad532c6ad80", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-6873 is fixed in version 4.2.post15+tuxcare of django." } }, { "id": "CVE-2026-8404", "affects": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ], "bom-ref": "urn:uuid:af391422-4be2-58f7-85e5-c2176b9117bd", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-8404 is fixed in version 4.2.post15+tuxcare of django." } } ], "dependencies": [ { "ref": "pkg:pypi/django@4.2.post15+tuxcare" } ] }