{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:8db81bbb-a658-5b39-970c-d21006ae4ef7", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "django", "purl": "pkg:pypi/django@4.2.post10+tuxcare", "type": "library", "bom-ref": "pkg:pypi/django@4.2.post10+tuxcare", "version": "4.2.post10+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.post10+tuxcare" } ], "bom-ref": "urn:uuid:7d2e90da-9732-5a61-9208-d90c4f9182c4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-31047 affects version 4.2.post10+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2023-36053", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:8d9d22ab-3a7d-5e21-801f-428165be473d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-36053 affects version 4.2.post10+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2023-41164", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:4f2a8a77-7dfb-55bc-bc10-f1f37926e5f3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-41164 affects version 4.2.post10+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2023-43665", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:d3d66b3b-f555-5a82-8f3c-dcb4c618f314", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-43665 affects version 4.2.post10+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2023-46695", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:2ce521a9-48e8-5379-8718-47e959288a55", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-46695 affects version 4.2.post10+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-24680", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:60a048da-2ea6-5137-8106-9be8ad85c337", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-24680 affects version 4.2.post10+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-27351", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:e6017c48-dbcb-52a0-8657-86160af244c3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-27351 affects version 4.2.post10+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-38875", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:f93eb204-62c9-585d-9b07-57cc18d46358", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-38875 affects version 4.2.post10+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-39329", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:c592fb44-8464-5577-8072-70ca6e17ae72", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-39329 affects version 4.2.post10+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-39330", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:bdac8658-cf0c-5b88-9767-3d59ad7273aa", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-39330 affects version 4.2.post10+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-39614", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:7f0a908d-3ff7-5a8f-82a8-d648268fb460", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-39614 affects version 4.2.post10+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-41989", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:9324a0d8-4626-5c2b-858b-efe527e8a001", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-41989 affects version 4.2.post10+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-41990", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:a7b7d30b-cd9d-53fa-8e65-1290a01e3603", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-41990 affects version 4.2.post10+tuxcare of django, and is fixed in 4.2.post18+tuxcare." } }, { "id": "CVE-2024-41991", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:f4a52df5-bf6a-57b5-b1a0-232065903902", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-41991 affects version 4.2.post10+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-42005", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:952404c2-ce46-5a21-a1f3-579a8f285835", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-42005 affects version 4.2.post10+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-45230", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:e5f0ae8c-6853-5c5c-8187-07b65ed8445a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-45230 affects version 4.2.post10+tuxcare of django, and is fixed in 4.2.post18+tuxcare." } }, { "id": "CVE-2024-45231", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:c033be92-a8fe-51de-be90-632ca69f6879", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-45231 affects version 4.2.post10+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-53907", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:7d205053-ca80-55f2-b448-8e7f7e4c9287", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-53907 affects version 4.2.post10+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-53908", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:86c79f79-bef5-573e-8812-616cb3e7b29e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-53908 affects version 4.2.post10+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-56374", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:0204e146-e279-51c4-a5f7-4f13a65e565a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-56374 affects version 4.2.post10+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2025-13372", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:16c44fc5-a4bc-58f1-a9b0-bb49039129cc", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13372 is fixed in version 4.2.post10+tuxcare of django." } }, { "id": "CVE-2025-13473", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:0582321b-6eb7-509a-95b0-ef4234eec619", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13473 is fixed in version 4.2.post10+tuxcare of django." } }, { "id": "CVE-2025-14550", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:bae54569-407c-5ce8-876f-6f3d223da27d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-14550 is fixed in version 4.2.post10+tuxcare of django." } }, { "id": "CVE-2025-26699", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:e65312f7-af1e-5bf8-a301-4e006f21de3f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-26699 affects version 4.2.post10+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2025-32873", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:dc4cb2cd-25d7-512e-b830-f6fb41e6cb72", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-32873 affects version 4.2.post10+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2025-48432", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:646ee4f6-6b8f-59ca-a892-fda2dad5cf49", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-48432 is fixed in version 4.2.post10+tuxcare of django." } }, { "id": "CVE-2025-57833", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:05a6317f-a795-5b23-9f0f-e48dd33b71d1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-57833 affects version 4.2.post10+tuxcare of django, and is fixed in 4.2.post12+tuxcare." } }, { "id": "CVE-2025-59681", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:29cecf06-7697-50fb-81f3-46064546bf0f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-59681 is fixed in version 4.2.post10+tuxcare of django." } }, { "id": "CVE-2025-59682", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:6c1e54b1-3a4b-5b95-9c34-5068ed839fdd", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-59682 is fixed in version 4.2.post10+tuxcare of django." } }, { "id": "CVE-2025-64458", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:3c88ecdb-d616-5a27-a0c5-2cf5e54b198f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64458 is fixed in version 4.2.post10+tuxcare of django." } }, { "id": "CVE-2025-64459", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:d847597d-4302-5366-8601-0caa35af0ada", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64459 is fixed in version 4.2.post10+tuxcare of django." } }, { "id": "CVE-2025-64460", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:f8533a21-93c6-5f20-983d-0bebbefa4fda", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64460 is fixed in version 4.2.post10+tuxcare of django." } }, { "id": "CVE-2026-1207", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:e051f243-3da1-5f9a-abc6-c31e9c5ee25d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1207 is fixed in version 4.2.post10+tuxcare of django." } }, { "id": "CVE-2026-1285", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:49dd7b4d-1d17-5603-804e-3d6772f328e3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1285 is fixed in version 4.2.post10+tuxcare of django." } }, { "id": "CVE-2026-1287", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:d4ecb286-2d72-543c-85c9-4164a0a136d1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1287 is fixed in version 4.2.post10+tuxcare of django." } }, { "id": "CVE-2026-1312", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:2408157b-2952-508a-b031-263742a33563", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1312 is fixed in version 4.2.post10+tuxcare of django." } }, { "id": "CVE-2026-15307", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:34f8940d-37fb-5550-84a6-08583fd63ee5", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-15307 affects version 4.2.post10+tuxcare of django, and is fixed in 4.2.post14+tuxcare." } }, { "id": "CVE-2026-15830", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:df91e7c5-ee62-58dc-8158-072980733730", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-15830 affects version 4.2.post10+tuxcare of django, and is fixed in 4.2.post14+tuxcare." } }, { "id": "CVE-2026-25673", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:230fe4df-ab26-52bf-9961-c3c22b2385e1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-25673 is fixed in version 4.2.post10+tuxcare of django." } }, { "id": "CVE-2026-25674", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:aacd4062-853d-5e2c-8f96-69a94b15b09a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-25674 is fixed in version 4.2.post10+tuxcare of django." } }, { "id": "CVE-2026-33033", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:14e9e495-101c-5989-bb87-a91d218b1959", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-33033 is fixed in version 4.2.post10+tuxcare of django." } }, { "id": "CVE-2026-33034", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:657817cb-7db9-571e-84d9-5552633559b1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-33034 is fixed in version 4.2.post10+tuxcare of django." } }, { "id": "CVE-2026-3902", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:b881156b-e3a3-59af-aa6b-f1f808ca1fd0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-3902 is fixed in version 4.2.post10+tuxcare of django." } }, { "id": "CVE-2026-4277", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:9a64fc9c-49bc-5d55-8d7c-3f26adb9c740", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-4277 is fixed in version 4.2.post10+tuxcare of django." } }, { "id": "CVE-2026-4292", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:b10a3c27-8e9c-5811-a3a3-fb71af083539", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-4292 is fixed in version 4.2.post10+tuxcare of django." } }, { "id": "CVE-2026-48587", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:91d5cfbf-de3d-5878-95cd-560eae67c636", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-48587 affects version 4.2.post10+tuxcare of django, and is fixed in 4.2.post12+tuxcare." } }, { "id": "CVE-2026-48588", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:eda9d88a-92c9-5703-9f14-47a8a456b25c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-48588 affects version 4.2.post10+tuxcare of django, and is fixed in 4.2.post11+tuxcare." } }, { "id": "CVE-2026-53877", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:a3fc4d25-7a1c-5e5b-8225-889481f9217e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-53877 affects version 4.2.post10+tuxcare of django, and is fixed in 4.2.post13+tuxcare." } }, { "id": "CVE-2026-53878", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:03ac32d3-74cc-53e3-ae78-ba65449f001f", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-53878 does not affect version 4.2.post10+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.post10+tuxcare" } ], "bom-ref": "urn:uuid:0273bc1b-eb6d-5dff-8a42-128094d696a2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-6873 affects version 4.2.post10+tuxcare of django, and is fixed in 4.2.post13+tuxcare." } }, { "id": "CVE-2026-8404", "affects": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ], "bom-ref": "urn:uuid:2fec6bcb-1c69-52de-a879-6c01b0ee29a6", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-8404 affects version 4.2.post10+tuxcare of django, and is fixed in 4.2.post11+tuxcare." } } ], "dependencies": [ { "ref": "pkg:pypi/django@4.2.post10+tuxcare" } ] }