{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:d62fbd27-c613-5930-998a-e992d12e3a79", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "django", "purl": "pkg:pypi/django@4.2.post14+tuxcare", "type": "library", "bom-ref": "pkg:pypi/django@4.2.post14+tuxcare", "version": "4.2.post14+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.post14+tuxcare" } ], "bom-ref": "urn:uuid:bc5b98a5-940d-5b42-ba25-aa225bf0b5a5", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-31047 affects version 4.2.post14+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2023-36053", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:2014fbdc-3fe2-5267-9cb4-3a125e24f39e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-36053 affects version 4.2.post14+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2023-41164", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:ae9df6e0-a83c-549d-ad31-46d56fd28302", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-41164 affects version 4.2.post14+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2023-43665", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:5de17125-d804-5534-8837-353942052cb3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-43665 affects version 4.2.post14+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2023-46695", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:e230ff0f-d608-5366-a577-39a28dc26c20", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-46695 affects version 4.2.post14+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-24680", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:c05109f6-ebe5-5b6b-ac62-032d5cccadbd", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-24680 affects version 4.2.post14+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-27351", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:a8360bf9-9401-5f10-9dc2-d7dc25d5b0e3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-27351 affects version 4.2.post14+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-38875", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:c4d5ef20-8c41-53ff-a999-42a715260812", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-38875 affects version 4.2.post14+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-39329", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:20757837-fdad-55aa-a3f1-48b58407f1b4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-39329 affects version 4.2.post14+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-39330", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:2ff402dd-a100-5d03-87c4-67f17238ff7e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-39330 affects version 4.2.post14+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-39614", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:53ff5f56-ba22-53a4-8a00-b48bba9bfe65", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-39614 affects version 4.2.post14+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-41989", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:7a364beb-d382-5135-89b8-b2ca7ec092ad", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-41989 affects version 4.2.post14+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-41990", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:2b210431-3c2c-54cd-aee6-f3b3215f4c9a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-41990 affects version 4.2.post14+tuxcare of django, and is fixed in 4.2.post18+tuxcare." } }, { "id": "CVE-2024-41991", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:72ef26a4-0e20-5c12-aa55-eddc457750de", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-41991 affects version 4.2.post14+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-42005", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:0edca8db-fea8-505d-bc60-337991f2c7ed", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-42005 affects version 4.2.post14+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-45230", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:7f49018f-eb9e-55e0-8b64-0eb97b79526a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-45230 affects version 4.2.post14+tuxcare of django, and is fixed in 4.2.post18+tuxcare." } }, { "id": "CVE-2024-45231", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:59728421-88ad-5e06-bc7b-b83c5ccac93d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-45231 affects version 4.2.post14+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-53907", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:5ee86a03-183c-5392-ad98-9301249998c7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-53907 affects version 4.2.post14+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-53908", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:4d4740fb-b80b-515a-af5c-696a78d39914", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-53908 affects version 4.2.post14+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2024-56374", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:40bee512-e792-56ab-b41b-e144ec91073a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-56374 affects version 4.2.post14+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2025-13372", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:05e30129-8f24-587e-b5f0-404220a549d5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13372 is fixed in version 4.2.post14+tuxcare of django." } }, { "id": "CVE-2025-13473", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:55a35f15-dfba-55eb-b58e-e88389bd5385", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13473 is fixed in version 4.2.post14+tuxcare of django." } }, { "id": "CVE-2025-14550", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:5d761e85-ad80-5049-8dc7-9579f2e82cb7", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-14550 is fixed in version 4.2.post14+tuxcare of django." } }, { "id": "CVE-2025-26699", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:21330e84-6f6a-5ae1-b0d7-fc7fa9281f90", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-26699 affects version 4.2.post14+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2025-32873", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:ff95cddd-dfb3-51ee-86ea-638d8926ec56", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-32873 affects version 4.2.post14+tuxcare of django, and is fixed in 4.2.post17+tuxcare." } }, { "id": "CVE-2025-48432", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:e310afb4-4185-55d3-a8b5-deb22b6f6ec3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-48432 is fixed in version 4.2.post14+tuxcare of django." } }, { "id": "CVE-2025-57833", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:f8765f93-c1be-5b6a-bf8c-0714d7b1537a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-57833 is fixed in version 4.2.post14+tuxcare of django." } }, { "id": "CVE-2025-59681", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:fce219ec-1822-5ec3-b40c-6780210b4c25", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-59681 is fixed in version 4.2.post14+tuxcare of django." } }, { "id": "CVE-2025-59682", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:ccb6f1a4-5e60-5774-8a28-bbac080e409f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-59682 is fixed in version 4.2.post14+tuxcare of django." } }, { "id": "CVE-2025-64458", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:58d72eac-78d0-5d52-b229-0f394f961922", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64458 is fixed in version 4.2.post14+tuxcare of django." } }, { "id": "CVE-2025-64459", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:8cf78892-e22d-5ae1-aac4-2d53133f15a3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64459 is fixed in version 4.2.post14+tuxcare of django." } }, { "id": "CVE-2025-64460", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:ef93fb47-3de6-502c-a643-0c3fb4cf6013", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64460 is fixed in version 4.2.post14+tuxcare of django." } }, { "id": "CVE-2026-1207", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:306fa9b6-65a1-578f-bf7d-5f1cea3ba616", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1207 is fixed in version 4.2.post14+tuxcare of django." } }, { "id": "CVE-2026-1285", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:36f9a752-9d3a-5961-afef-b9a651167714", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1285 is fixed in version 4.2.post14+tuxcare of django." } }, { "id": "CVE-2026-1287", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:dbf5ad85-68c3-58be-9dcd-a6b7435ae2ef", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1287 is fixed in version 4.2.post14+tuxcare of django." } }, { "id": "CVE-2026-1312", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:64499bbc-6c32-553b-8537-0bf6148443e5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1312 is fixed in version 4.2.post14+tuxcare of django." } }, { "id": "CVE-2026-15307", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:566146c7-938a-533b-8a4f-ddfd41324385", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15307 is fixed in version 4.2.post14+tuxcare of django." } }, { "id": "CVE-2026-15830", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:b69f1ee8-2c4d-550b-8b8b-53a5de93a012", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15830 is fixed in version 4.2.post14+tuxcare of django." } }, { "id": "CVE-2026-25673", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:310b38e6-8d78-569f-8fd5-310fc539e983", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-25673 is fixed in version 4.2.post14+tuxcare of django." } }, { "id": "CVE-2026-25674", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:40453568-8ff3-55a7-a3ad-db8863064418", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-25674 is fixed in version 4.2.post14+tuxcare of django." } }, { "id": "CVE-2026-33033", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:6b885dec-c1a3-5edd-8eb6-7f06697122a7", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-33033 is fixed in version 4.2.post14+tuxcare of django." } }, { "id": "CVE-2026-33034", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:9a28d06d-cde6-5a81-89d1-0f152a49dbf1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-33034 is fixed in version 4.2.post14+tuxcare of django." } }, { "id": "CVE-2026-3902", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:d31cff60-c74c-5c90-9b73-b88b057edfd5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-3902 is fixed in version 4.2.post14+tuxcare of django." } }, { "id": "CVE-2026-4277", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:24d06195-3150-5764-9820-9f43ceee8879", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-4277 is fixed in version 4.2.post14+tuxcare of django." } }, { "id": "CVE-2026-4292", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:7efcf736-8ff2-50cf-82b2-e8c54e21f305", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-4292 is fixed in version 4.2.post14+tuxcare of django." } }, { "id": "CVE-2026-48587", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:bfbdb1aa-4e7a-565f-aecf-6d864ee4579e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48587 is fixed in version 4.2.post14+tuxcare of django." } }, { "id": "CVE-2026-48588", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:6e69bc06-0201-539b-a633-18adc8dc6aff", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48588 is fixed in version 4.2.post14+tuxcare of django." } }, { "id": "CVE-2026-53877", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:fe90a27b-4b59-5a0a-87c8-a0414a68e82c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-53877 is fixed in version 4.2.post14+tuxcare of django." } }, { "id": "CVE-2026-53878", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:46fd3b40-1b76-5726-b3b3-702fe5182849", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-53878 does not affect version 4.2.post14+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.post14+tuxcare" } ], "bom-ref": "urn:uuid:7af01b50-78e0-5be8-946e-a173ee212d45", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-6873 is fixed in version 4.2.post14+tuxcare of django." } }, { "id": "CVE-2026-8404", "affects": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ], "bom-ref": "urn:uuid:f99fcfa2-1302-5a51-8408-6a72e3544095", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-8404 is fixed in version 4.2.post14+tuxcare of django." } } ], "dependencies": [ { "ref": "pkg:pypi/django@4.2.post14+tuxcare" } ] }