{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:0386d0a7-ce04-506f-9e98-57e3fa1912e5", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "django", "purl": "pkg:pypi/django@4.2.post11+tuxcare", "type": "library", "bom-ref": "pkg:pypi/django@4.2.post11+tuxcare", "version": "4.2.post11+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.post11+tuxcare" } ], "bom-ref": "urn:uuid:4b2d01b9-55f9-516c-a187-32b9d82356c1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-31047 affects version 4.2.post11+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2023-36053", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:1c5e3d2d-f1de-57cc-986c-2eda08bd33ec", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-36053 affects version 4.2.post11+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2023-41164", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:aaffefd8-f7e1-5ad8-9d6b-f1334ad1c453", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-41164 affects version 4.2.post11+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2023-43665", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:93d829e8-6a4c-5edf-b281-fb94224d9582", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-43665 affects version 4.2.post11+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2023-46695", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:af7eae93-7ea0-55b2-ae75-3028479d4263", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-46695 affects version 4.2.post11+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-24680", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:6ea0dedf-d172-5c2d-9acb-965541f1df1b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-24680 affects version 4.2.post11+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-27351", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:70a8029d-803e-5f6e-8512-f8a66700ecb9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-27351 affects version 4.2.post11+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-38875", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:0b3c174e-66ca-5297-b429-14aff4cf1e07", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-38875 affects version 4.2.post11+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-39329", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:0d0f2dfd-800b-585b-8715-0fb3a3ec0479", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-39329 affects version 4.2.post11+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-39330", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:b774d0b5-89de-5659-9a08-59aee03ce265", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-39330 affects version 4.2.post11+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-39614", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:ac24cab2-760f-5753-8c91-cf5f3a070547", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-39614 affects version 4.2.post11+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-41989", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:f08aa62c-2387-54b6-b3e2-2cbb3b02398d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-41989 affects version 4.2.post11+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-41990", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:9fb68499-c350-536e-a948-6581c640db80", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-41990 affects version 4.2.post11+tuxcare of django, and is fixed in 4.2.post18+tuxcare." } }, { "id": "CVE-2024-41991", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:f4fcd49b-c05b-529e-935b-f90a3aa96761", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-41991 affects version 4.2.post11+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-42005", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:9abd66e5-80cd-5406-bafb-0613ced63d56", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-42005 affects version 4.2.post11+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-45230", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:72e5e619-40ca-56b7-8653-0df39d89d5b7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-45230 affects version 4.2.post11+tuxcare of django, and is fixed in 4.2.post18+tuxcare." } }, { "id": "CVE-2024-45231", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:9840d174-b2c4-5ea2-8011-a5634aec2938", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-45231 affects version 4.2.post11+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-53907", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:f34ddf21-fb39-5921-b9bb-9035659c73c5", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-53907 affects version 4.2.post11+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-53908", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:1ff6aeaf-4f7c-5c74-81f2-e937ec6b6b4b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-53908 affects version 4.2.post11+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-56374", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:760bfcd4-ced7-53f6-a738-1f8c3b3995be", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-56374 affects version 4.2.post11+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2025-13372", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:1b0f18a3-7068-5bf7-a4a7-14bf6e73845b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13372 is fixed in version 4.2.post11+tuxcare of django." } }, { "id": "CVE-2025-13473", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:3ff945fa-fd36-5800-8a1b-4ea4edb5c771", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13473 is fixed in version 4.2.post11+tuxcare of django." } }, { "id": "CVE-2025-14550", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:170a5be2-1fb9-563c-a056-e24dbc1e8bc5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-14550 is fixed in version 4.2.post11+tuxcare of django." } }, { "id": "CVE-2025-26699", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:06c3ba7c-da47-5927-8a49-bdd2f4b0b0be", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-26699 affects version 4.2.post11+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2025-32873", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:b1d0f0aa-1ee1-538b-a883-d33b98339e93", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-32873 affects version 4.2.post11+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2025-48432", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:ea417dde-0574-5381-9468-661cb9585e1a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-48432 is fixed in version 4.2.post11+tuxcare of django." } }, { "id": "CVE-2025-57833", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:30f68d12-8421-5180-80ec-f4da537a0ff3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-57833 affects version 4.2.post11+tuxcare of django, and is fixed in 4.2.post12+tuxcare." } }, { "id": "CVE-2025-59681", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:5166c8dd-2641-5f40-ad83-c4856b7ee29a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-59681 is fixed in version 4.2.post11+tuxcare of django." } }, { "id": "CVE-2025-59682", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:6c82fc8f-3655-5429-84ce-136f58277889", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-59682 is fixed in version 4.2.post11+tuxcare of django." } }, { "id": "CVE-2025-64458", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:f54eb434-dd44-5e8d-b290-f74915458b68", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64458 is fixed in version 4.2.post11+tuxcare of django." } }, { "id": "CVE-2025-64459", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:a88d983a-30a2-52c5-bd68-4a9aff4d95f4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64459 is fixed in version 4.2.post11+tuxcare of django." } }, { "id": "CVE-2025-64460", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:2e966c11-ea1e-5755-87e8-3e70fffad7ee", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64460 is fixed in version 4.2.post11+tuxcare of django." } }, { "id": "CVE-2026-1207", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:6ace911a-0e2c-5b37-8fcf-a47d248a5215", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1207 is fixed in version 4.2.post11+tuxcare of django." } }, { "id": "CVE-2026-1285", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:a2dfdaf0-a11c-5827-b64e-f994b379c4a0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1285 is fixed in version 4.2.post11+tuxcare of django." } }, { "id": "CVE-2026-1287", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:2815cc80-9687-5cb5-9fe3-0ff4d8fae468", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1287 is fixed in version 4.2.post11+tuxcare of django." } }, { "id": "CVE-2026-1312", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:4a37f25a-7ef7-530c-bdb0-486a2f0d9ffb", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1312 is fixed in version 4.2.post11+tuxcare of django." } }, { "id": "CVE-2026-15307", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:f707c522-928c-5b8d-b596-badc54e9d078", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-15307 affects version 4.2.post11+tuxcare of django, and is fixed in 4.2.post14+tuxcare." } }, { "id": "CVE-2026-15830", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:b41d1b47-289e-5516-99bc-f156b4672fc6", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-15830 affects version 4.2.post11+tuxcare of django, and is fixed in 4.2.post14+tuxcare." } }, { "id": "CVE-2026-25673", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:2a8f6184-fbba-512b-9c89-090b1bd6558d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-25673 is fixed in version 4.2.post11+tuxcare of django." } }, { "id": "CVE-2026-25674", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:b065b78d-fe8f-5bd5-b641-c8aecd737e8c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-25674 is fixed in version 4.2.post11+tuxcare of django." } }, { "id": "CVE-2026-33033", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:5c5b8013-58a4-5aa8-9f8c-6ad9a0a4db5f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-33033 is fixed in version 4.2.post11+tuxcare of django." } }, { "id": "CVE-2026-33034", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:44557000-8efd-54a8-97f9-d9f1e1f405ec", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-33034 is fixed in version 4.2.post11+tuxcare of django." } }, { "id": "CVE-2026-3902", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:e2e7a22f-c546-5b70-bb66-57255d3db2ad", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-3902 is fixed in version 4.2.post11+tuxcare of django." } }, { "id": "CVE-2026-4277", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:5219572a-9bac-5cde-8fec-6689b599fc1e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-4277 is fixed in version 4.2.post11+tuxcare of django." } }, { "id": "CVE-2026-4292", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:82a2bac2-c8d2-53ba-b79e-8c560c56f9b2", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-4292 is fixed in version 4.2.post11+tuxcare of django." } }, { "id": "CVE-2026-48587", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:9f524353-d789-5305-88a9-4a9cb91d74b2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-48587 affects version 4.2.post11+tuxcare of django, and is fixed in 4.2.post12+tuxcare." } }, { "id": "CVE-2026-48588", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:8d86f5d8-b17e-52dd-a552-fb3ceb3e5d10", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48588 is fixed in version 4.2.post11+tuxcare of django." } }, { "id": "CVE-2026-53877", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:a7f66238-7fe8-5b7c-91bb-e07d96c8de9c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-53877 affects version 4.2.post11+tuxcare of django, and is fixed in 4.2.post13+tuxcare." } }, { "id": "CVE-2026-53878", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:de4a92c7-8711-528d-b6d0-da1e482e582e", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-53878 does not affect version 4.2.post11+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.post11+tuxcare" } ], "bom-ref": "urn:uuid:feb55436-70ac-5bdf-8adc-c76508977b36", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-6873 affects version 4.2.post11+tuxcare of django, and is fixed in 4.2.post13+tuxcare." } }, { "id": "CVE-2026-8404", "affects": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:78f27625-2b44-530e-abc4-24626be3d7c1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-8404 is fixed in version 4.2.post11+tuxcare of django." } } ], "dependencies": [ { "ref": "pkg:pypi/django@4.2.post11+tuxcare" } ] }