{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:a4d63e55-fea7-57ed-a240-b6f8d676855e", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "django", "purl": "pkg:pypi/django@4.2.post16+tuxcare", "type": "library", "bom-ref": "pkg:pypi/django@4.2.post16+tuxcare", "version": "4.2.post16+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.post16+tuxcare" } ], "bom-ref": "urn:uuid:0214cbab-600d-5b14-a7b9-c0a1c0ad4a80", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-31047 affects version 4.2.post16+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2023-36053", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:bc8f10f1-f52c-5cdb-a36d-bd29c23653cc", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-36053 affects version 4.2.post16+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2023-41164", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:664c3b19-88b9-5aec-a1bf-42d2368b8f80", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-41164 affects version 4.2.post16+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2023-43665", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:090f27bd-8feb-5b3b-b43b-c850c40c2c5b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-43665 affects version 4.2.post16+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2023-46695", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:a71ce29a-61ca-55ab-b26e-b8beebc40c3b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-46695 affects version 4.2.post16+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-24680", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:70a2a86b-3dc6-51f7-819d-98c484d68fb1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-24680 affects version 4.2.post16+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-27351", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:23f28dbb-6f6b-5f20-af2f-41f99071adf4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-27351 affects version 4.2.post16+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-38875", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:b4a96524-a78f-596e-aef6-55e90e37317e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-38875 affects version 4.2.post16+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-39329", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:6e396ff4-aedf-5c66-b776-4444920e8cf0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-39329 affects version 4.2.post16+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-39330", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:45c7a752-2cc8-5280-b8f8-b6c4202b5412", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-39330 affects version 4.2.post16+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-39614", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:cae613a0-05bd-5688-aa74-8c7bdcb131e0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-39614 affects version 4.2.post16+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-41989", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:57a65d35-7292-572c-9910-0020c7640720", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-41989 affects version 4.2.post16+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-41990", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:3395c5f6-05b3-5358-8932-e2c6faa5ea34", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-41990 affects version 4.2.post16+tuxcare of django, and is fixed in 4.2.post18+tuxcare." } }, { "id": "CVE-2024-41991", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:ab7e0a18-a0ee-5c38-a95a-19453677a0d4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-41991 affects version 4.2.post16+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-42005", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:b959ab42-805e-501f-9372-abc0f5b095b4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-42005 affects version 4.2.post16+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-45230", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:e6c3ba31-a212-5ef4-8c7c-6b334ef9dccb", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-45230 affects version 4.2.post16+tuxcare of django, and is fixed in 4.2.post18+tuxcare." } }, { "id": "CVE-2024-45231", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:c2752bdf-913f-540e-9cdb-f1ce0477f949", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-45231 affects version 4.2.post16+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-53907", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:ea042f93-c2dd-5463-a1bb-d6a18224ce24", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-53907 affects version 4.2.post16+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-53908", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:5c35e7ba-9e42-5fcb-9372-f3adc4fd2cc5", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-53908 affects version 4.2.post16+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-56374", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:2a050d24-dfbb-59b7-8aac-2442e934a8f6", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-56374 affects version 4.2.post16+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2025-13372", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:3e5c3b92-04c5-53f1-83c8-aef1b227111c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13372 is fixed in version 4.2.post16+tuxcare of django." } }, { "id": "CVE-2025-13473", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:9d3d9271-ef4d-502c-81fd-134e25111e4b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13473 is fixed in version 4.2.post16+tuxcare of django." } }, { "id": "CVE-2025-14550", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:6c66c9d6-2041-5d3a-90cb-d710dd0043e5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-14550 is fixed in version 4.2.post16+tuxcare of django." } }, { "id": "CVE-2025-26699", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:2cd07327-b71a-553a-9c5a-cdbdf0e2f3a5", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-26699 affects version 4.2.post16+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2025-32873", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:a7a93ac4-d718-5cb9-9ba1-434cf9e732b2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-32873 affects version 4.2.post16+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2025-48432", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:f7bdcbf5-e0a4-5ba5-9698-6907128ac65d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-48432 is fixed in version 4.2.post16+tuxcare of django." } }, { "id": "CVE-2025-57833", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:079ce958-1936-5290-9459-da81473fe437", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-57833 is fixed in version 4.2.post16+tuxcare of django." } }, { "id": "CVE-2025-59681", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:f409cc2f-78fe-52fd-9da3-ba8e6014ea22", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-59681 is fixed in version 4.2.post16+tuxcare of django." } }, { "id": "CVE-2025-59682", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:50c1d8a7-f068-5467-89cf-80e445a33906", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-59682 is fixed in version 4.2.post16+tuxcare of django." } }, { "id": "CVE-2025-64458", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:7115d9be-94cb-571e-8541-8eba9cf69208", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64458 is fixed in version 4.2.post16+tuxcare of django." } }, { "id": "CVE-2025-64459", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:6169ea79-081c-5afd-860f-49b88e365f2d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64459 is fixed in version 4.2.post16+tuxcare of django." } }, { "id": "CVE-2025-64460", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:c6df8f4d-974a-5c81-ae09-c53cf52b7e59", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64460 is fixed in version 4.2.post16+tuxcare of django." } }, { "id": "CVE-2026-1207", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:16d1d3fe-c0ee-5b05-b1e0-d6427ef125a5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1207 is fixed in version 4.2.post16+tuxcare of django." } }, { "id": "CVE-2026-1285", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:fbea59f6-45d9-5518-8d63-7b7bba48e6a2", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1285 is fixed in version 4.2.post16+tuxcare of django." } }, { "id": "CVE-2026-1287", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:0ab5820c-8838-56a6-9dc1-df7cb0bf0ee5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1287 is fixed in version 4.2.post16+tuxcare of django." } }, { "id": "CVE-2026-1312", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:dd8c1cf0-9a7f-5a24-9623-9a7d63115d8f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1312 is fixed in version 4.2.post16+tuxcare of django." } }, { "id": "CVE-2026-15307", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:b9aa3665-cdb1-5827-ad4c-10f8146fda13", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15307 is fixed in version 4.2.post16+tuxcare of django." } }, { "id": "CVE-2026-15830", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:bbd936f5-eb6f-5fb5-9684-629f6700adfe", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15830 is fixed in version 4.2.post16+tuxcare of django." } }, { "id": "CVE-2026-25673", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:96b76186-eb17-5543-8d88-adec6098781e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-25673 is fixed in version 4.2.post16+tuxcare of django." } }, { "id": "CVE-2026-25674", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:6772c47d-7db6-50ac-9c9c-50e13fd75ba8", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-25674 is fixed in version 4.2.post16+tuxcare of django." } }, { "id": "CVE-2026-33033", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:8bc41c5a-8911-52a5-ab79-e5a7893ee449", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-33033 is fixed in version 4.2.post16+tuxcare of django." } }, { "id": "CVE-2026-33034", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:488a4fc1-325e-5b2c-af2d-e6dbac61f12b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-33034 is fixed in version 4.2.post16+tuxcare of django." } }, { "id": "CVE-2026-3902", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:62337314-1845-507f-8e3e-4cfaed587f00", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-3902 is fixed in version 4.2.post16+tuxcare of django." } }, { "id": "CVE-2026-4277", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:8f8d29fc-3cc6-5f2c-a1db-edf45a9f2cd4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-4277 is fixed in version 4.2.post16+tuxcare of django." } }, { "id": "CVE-2026-4292", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:a1dbcead-e450-5efd-b18c-44b64bb7b569", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-4292 is fixed in version 4.2.post16+tuxcare of django." } }, { "id": "CVE-2026-48587", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:7d42d963-4103-5e98-8390-5a8e0f9d3c9a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48587 is fixed in version 4.2.post16+tuxcare of django." } }, { "id": "CVE-2026-48588", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:351901b6-8aa2-54b8-b45d-8eb399df9371", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48588 is fixed in version 4.2.post16+tuxcare of django." } }, { "id": "CVE-2026-53877", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:295bb461-2d19-5cfe-b917-de334dd01832", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-53877 is fixed in version 4.2.post16+tuxcare of django." } }, { "id": "CVE-2026-53878", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:024fbf75-1648-54d3-ae9f-016a191a406f", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-53878 does not affect version 4.2.post16+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.post16+tuxcare" } ], "bom-ref": "urn:uuid:ccf666b3-3f18-512c-94c4-963464ca3f7a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-6873 is fixed in version 4.2.post16+tuxcare of django." } }, { "id": "CVE-2026-8404", "affects": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ], "bom-ref": "urn:uuid:e5396aca-f9f1-5d45-9c9d-e89e07f6efbf", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-8404 is fixed in version 4.2.post16+tuxcare of django." } } ], "dependencies": [ { "ref": "pkg:pypi/django@4.2.post16+tuxcare" } ] }