{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:6752da24-007e-5ce4-86b1-57ea280019b8", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "django", "purl": "pkg:pypi/django@5.1.10.post5+tuxcare", "type": "library", "bom-ref": "pkg:pypi/django@5.1.10.post5+tuxcare", "version": "5.1.10.post5+tuxcare", "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2025-13372", "affects": [ { "ref": "pkg:pypi/django@5.1.10.post5+tuxcare" } ], "bom-ref": "urn:uuid:cf53a767-5550-5143-a257-d7233944cd17", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13372 is fixed in version 5.1.10.post5+tuxcare of django." } }, { "id": "CVE-2025-13473", "affects": [ { "ref": "pkg:pypi/django@5.1.10.post5+tuxcare" } ], "bom-ref": "urn:uuid:bfb9d4a3-5586-57ac-9fd2-47665c49279c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13473 is fixed in version 5.1.10.post5+tuxcare of django." } }, { "id": "CVE-2025-14550", "affects": [ { "ref": "pkg:pypi/django@5.1.10.post5+tuxcare" } ], "bom-ref": "urn:uuid:cce40d8d-b72d-5d83-baf6-52d17eee669d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-14550 is fixed in version 5.1.10.post5+tuxcare of django." } }, { "id": "CVE-2025-57833", "affects": [ { "ref": "pkg:pypi/django@5.1.10.post5+tuxcare" } ], "bom-ref": "urn:uuid:16ee9da4-5cf6-56d8-9206-25ac0dbe5c9f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-57833 is fixed in version 5.1.10.post5+tuxcare of django." } }, { "id": "CVE-2025-59681", "affects": [ { "ref": "pkg:pypi/django@5.1.10.post5+tuxcare" } ], "bom-ref": "urn:uuid:d9061c8f-0fd5-5559-a71e-2b581db83722", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-59681 is fixed in version 5.1.10.post5+tuxcare of django." } }, { "id": "CVE-2025-59682", "affects": [ { "ref": "pkg:pypi/django@5.1.10.post5+tuxcare" } ], "bom-ref": "urn:uuid:3013a66d-87ec-5210-9a86-ecc38658d20e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-59682 is fixed in version 5.1.10.post5+tuxcare of django." } }, { "id": "CVE-2025-64458", "affects": [ { "ref": "pkg:pypi/django@5.1.10.post5+tuxcare" } ], "bom-ref": "urn:uuid:1cb3f8b4-a1f1-5e3d-8045-2d078b18f03e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64458 is fixed in version 5.1.10.post5+tuxcare of django." } }, { "id": "CVE-2025-64459", "affects": [ { "ref": "pkg:pypi/django@5.1.10.post5+tuxcare" } ], "bom-ref": "urn:uuid:796c8759-af6f-5490-b459-e05cd1fb3cd5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64459 is fixed in version 5.1.10.post5+tuxcare of django." } }, { "id": "CVE-2025-64460", "affects": [ { "ref": "pkg:pypi/django@5.1.10.post5+tuxcare" } ], "bom-ref": "urn:uuid:664c8b41-7d00-58a9-b84f-a339b512185a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64460 is fixed in version 5.1.10.post5+tuxcare of django." } }, { "id": "CVE-2026-1207", "affects": [ { "ref": "pkg:pypi/django@5.1.10.post5+tuxcare" } ], "bom-ref": "urn:uuid:88be50f3-5d32-5606-8764-aa6121ed3921", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1207 is fixed in version 5.1.10.post5+tuxcare of django." } }, { "id": "CVE-2026-1285", "affects": [ { "ref": "pkg:pypi/django@5.1.10.post5+tuxcare" } ], "bom-ref": "urn:uuid:24c63483-0d39-5d55-8ae1-152f26cf21b5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1285 is fixed in version 5.1.10.post5+tuxcare of django." } }, { "id": "CVE-2026-1287", "affects": [ { "ref": "pkg:pypi/django@5.1.10.post5+tuxcare" } ], "bom-ref": "urn:uuid:719b69b0-6e40-5f59-9571-d0096562da34", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1287 is fixed in version 5.1.10.post5+tuxcare of django." } }, { "id": "CVE-2026-1312", "affects": [ { "ref": "pkg:pypi/django@5.1.10.post5+tuxcare" } ], "bom-ref": "urn:uuid:fc440288-8ce1-5f61-b3f4-1d15b23c2a69", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1312 is fixed in version 5.1.10.post5+tuxcare of django." } }, { "id": "CVE-2026-15307", "affects": [ { "ref": "pkg:pypi/django@5.1.10.post5+tuxcare" } ], "bom-ref": "urn:uuid:1eb786a0-025e-5aec-8a99-9bf6d69afe62", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15307 is fixed in version 5.1.10.post5+tuxcare of django." } }, { "id": "CVE-2026-15830", "affects": [ { "ref": "pkg:pypi/django@5.1.10.post5+tuxcare" } ], "bom-ref": "urn:uuid:0f9b4634-6796-5d5c-95ea-7a4061872abe", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15830 is fixed in version 5.1.10.post5+tuxcare of django." } }, { "id": "CVE-2026-48587", "affects": [ { "ref": "pkg:pypi/django@5.1.10.post5+tuxcare" } ], "bom-ref": "urn:uuid:2c9bf9c0-337e-5f38-b960-90a0b4ebd079", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48587 is fixed in version 5.1.10.post5+tuxcare of django." } }, { "id": "CVE-2026-48588", "affects": [ { "ref": "pkg:pypi/django@5.1.10.post5+tuxcare" } ], "bom-ref": "urn:uuid:626ab92e-9631-5ae3-bb60-a73fdac9bffe", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48588 is fixed in version 5.1.10.post5+tuxcare of django." } }, { "id": "CVE-2026-53877", "affects": [ { "ref": "pkg:pypi/django@5.1.10.post5+tuxcare" } ], "bom-ref": "urn:uuid:0f4a35ab-9203-5dd9-96c3-cac3d950d2df", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-53877 is fixed in version 5.1.10.post5+tuxcare of django." } }, { "id": "CVE-2026-53878", "affects": [ { "ref": "pkg:pypi/django@5.1.10.post5+tuxcare" } ], "bom-ref": "urn:uuid:7930be51-0bfa-56c7-826c-f612b4a1dcea", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-53878 does not affect version 5.1.10.post5+tuxcare of django. not_affected \u2014 Django 5.1.10 is not affected by CVE-2026-53878. While DomainNameValidator does accept domain names with trailing newlines (due to Python regex '$' matching before newlines), Django itself is protected by HttpResponse's runtime newline checks. All HTTP responses in Django go through ResponseHeaders._convert_to_charset() which explicitly checks for and rejects '\\n' and '\\r' characters in header ...", "justification": "protected_at_runtime" } }, { "id": "CVE-2026-6873", "affects": [ { "ref": "pkg:pypi/django@5.1.10.post5+tuxcare" } ], "bom-ref": "urn:uuid:a6682d5c-d91b-5ed6-8084-8040b979b4ea", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-6873 is fixed in version 5.1.10.post5+tuxcare of django." } }, { "id": "CVE-2026-8404", "affects": [ { "ref": "pkg:pypi/django@5.1.10.post5+tuxcare" } ], "bom-ref": "urn:uuid:586cc305-8f56-51ce-a0d4-07beefefd90d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-8404 is fixed in version 5.1.10.post5+tuxcare of django." } } ], "dependencies": [ { "ref": "pkg:pypi/django@5.1.10.post5+tuxcare" } ] }