{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:5c196768-392e-57b6-80c1-5fcf310e8c23", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "django", "purl": "pkg:pypi/django@5.0.2.post11+tuxcare", "type": "library", "bom-ref": "pkg:pypi/django@5.0.2.post11+tuxcare", "version": "5.0.2.post11+tuxcare", "pedigree": { "ancestors": [ { "name": "django", "purl": "pkg:pypi/django@5.0.2", "type": "library", "version": "5.0.2" } ] }, "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2021-45115", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:699106ef-555c-5e72-82e3-050d5bc50521", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-45115 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2021-45116", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:2f4dda3e-b324-5d28-85b4-f91bea7359da", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-45116 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2021-45452", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:20e2360a-4881-5325-a41e-7f1e0c249756", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2021-45452 does not affect version 5.0.2.post11+tuxcare of django. not_affected \u2014 Django 5.0.2 is NOT affected by CVE-2021-45452. The directory traversal vulnerability in Storage.save() was fixed by upstream Django in version 4.0.1 (January 2022), over 2 years before Django 5.0.2 was released (February 2024). All required defenses are present in the target: backslash normalization, path traversal detection via \"..\" checks, os.path.relpath() to ensure relative paths, and trip...", "justification": "code_not_present" } }, { "id": "CVE-2022-22818", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:1b2e6bb2-adb7-552b-a195-09f05c80e14f", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2022-22818 does not affect version 5.0.2.post11+tuxcare of django. not_affected \u2014 Target Django 5.0.2 is not affected by CVE-2022-22818. The vulnerability (unescaped HTML output in {% debug %} template tag leading to XSS) is not present because the upstream Django fix was already included in the 5.0.2 release. The DebugNode.render() method contains both security measures: (1) early return when DEBUG=False, and (2) HTML escaping via escape() on all pformat outputs. CVE affect...", "justification": "code_not_present" } }, { "id": "CVE-2022-23833", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:29536f80-34d8-5b5c-b4c9-349fc0585e0d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-23833 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2022-28346", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:42484094-9f04-5ad2-bdec-97045d89b3d7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-28346 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2022-28347", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:12700030-3e29-5f1e-ab59-a91878a63184", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-28347 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2022-34265", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:80357817-6de1-54f9-ac1a-f51e05635281", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-34265 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2022-36359", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:3357e846-8757-56e2-96dd-264125987352", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-36359 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2022-41323", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:86d9b5a4-5ca3-59b3-83bb-498cb518b457", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-41323 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2023-23969", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:dd961d73-6732-5cb4-ab42-fb24585fe4e3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-23969 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2023-24580", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:44f0b2b1-d280-57f7-82a8-a9412b034b3e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-24580 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2023-31047", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:4c6c0cc1-b103-56d6-b662-79cacd0d869c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-31047 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2023-36053", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:7fa868f0-c4f6-58be-992f-d861fa8affda", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-36053 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2023-41164", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:54876906-0fb5-547c-b6c7-eb67f66e52ed", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-41164 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2023-43665", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:2b6deb53-b702-5a7c-ae14-b33e84bcaddb", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-43665 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2023-46695", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:7af6837d-c7a3-59f9-88f9-b28450ea20a5", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-46695 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2024-24680", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:30a6124e-be51-5e3d-9b60-6888a9036054", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-24680 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2024-27351", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:8d2fedcc-bb18-5b6b-b2da-2289aaae7523", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-27351 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2024-38875", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:85212a61-3dab-5126-b782-ceabd98b3709", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-38875 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2024-39329", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:8a8269f5-2dae-5244-a500-c4d90d7d9001", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39329 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2024-39330", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:30e836ff-bc4c-5278-a015-a0b8af82cd25", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39330 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2024-39614", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:8ac4053b-24af-5222-ab41-e27b62b4cf61", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39614 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2024-41989", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:04475b98-7d62-5e51-a414-e9399c18c913", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-41989 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2024-41990", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:043cef8a-86f3-56ac-9c34-8831833a556d", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2024-41990 does not affect version 5.0.2.post11+tuxcare of django. not_affected \u2014 Django 5.0.2 uses the original simple trim_punctuation implementation that lacks the vulnerable code pattern. CVE-2024-41990's DoS vulnerability was introduced by the CVE-2024-38875 fix (commit d666457453, June 2024) which replaced the simple implementation with a complex CountsDict-based one containing repeated rfind('&') calls. The target version predates this architectural change and therefo...", "justification": "code_not_present" } }, { "id": "CVE-2024-41991", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:dac4c20c-5a0b-578d-9b36-d8024846f147", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-41991 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2024-42005", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:dd35f60a-0e0d-5d33-b7dd-ccfbcc6b778d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-42005 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2024-45230", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:98487094-2748-5b07-aa1e-168318824521", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-45230 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2024-45231", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:3dcd2473-0521-509a-93c1-986f00c1efb6", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-45231 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2024-53907", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:5c7118ff-6284-5a8e-a1b7-671a8ecc5886", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-53907 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2024-53908", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:5e9bd4f9-76e1-5fb5-8dbf-f4828334d7d4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-53908 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2024-56374", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:0aa0e199-236d-5221-99bc-9d7d0da2e40f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-56374 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2025-13372", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:8049cea9-6de3-5636-b1c1-186ac85762c0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13372 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2025-13473", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:e9462130-a8c8-5bbf-bfad-f5bec8baff2c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13473 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2025-14550", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:7f86b186-2570-5230-8da3-d6d33d16ea8b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-14550 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2025-26699", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:615a123e-7ec2-545e-b2ab-b6a030b93408", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-26699 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2025-27556", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:01926c81-3364-5382-b94c-4dce2cf4a30b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-27556 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2025-32873", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:5674235e-50a4-5cbd-83c0-a96d6626a9a0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-32873 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2025-48432", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:c75ff64c-470a-5f73-ae66-6f2f2b5237a5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-48432 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2025-57833", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:81df920e-94e9-5e71-8194-bdeebff0ebcd", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-57833 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2025-59681", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:8f8add7f-be44-5e88-aef9-efab39fea876", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-59681 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2025-59682", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:afda2b5f-a3aa-5d60-a308-abd3b1365c96", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-59682 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2025-64458", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:8822addf-9d77-55f7-8381-00cf55abe2ce", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64458 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2025-64459", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:13a81706-1ccb-5061-93bf-33cb6ba3d9b0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64459 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2025-64460", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:9eb166af-eea9-50bc-9ad2-699b36cda16c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64460 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-1207", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:c3a53b81-0189-5b8c-b2fa-49e1d623d0bb", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1207 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-1285", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:18acf11d-00ef-52c4-8d98-80125c6bdc49", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-1285 affects version 5.0.2.post11+tuxcare of django, and is fixed in 5.0.2.post12+tuxcare." } }, { "id": "CVE-2026-1287", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:6a54f641-91d4-512c-8298-1d98517e6b3d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1287 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-1312", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:6d13c0cf-01ff-56f4-91ea-7cd813550fd1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1312 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-15307", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:6f23cb45-11c1-5a8a-8985-ee08383a3ecf", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15307 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-15830", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:001df9f6-6f6c-5f82-89fd-e5ca2e1fc298", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15830 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-25673", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:1f7d2b51-5595-5a49-9555-45cf2bbb2354", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-25673 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-25674", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:c262ee05-4158-509b-b916-0ea0ee9063d4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-25674 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-33033", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:63db3dbc-3de5-533c-a465-48df3b82d05c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33033 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-33034", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:9e2eb1f7-1531-5ae5-8617-b3262811fc2c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33034 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-3902", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:3766c3eb-fd65-5cbe-94fe-ede3ca89d7d9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-3902 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-4277", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:605af7aa-bda6-51ab-a2f4-48b4e0ba642b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-4277 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-4292", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:75401077-e8c4-5a88-a7b5-dfe7069bca51", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-4292 affects version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-48587", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:db0b421f-bd97-5972-90f3-a1aad4ab70c4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48587 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-48588", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:bd40b186-7829-50aa-8d0c-66fddf1e0fdd", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48588 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-53877", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:f3453d91-ab3c-5f12-82cd-39bd1636dfa6", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-53877 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-53878", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:f81dc1ec-ec80-5530-86ce-e0ede7071ed6", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-53878 does not affect version 5.0.2.post11+tuxcare of django. not_affected \u2014 Django 5.0.2 is not affected by CVE-2026-53878. The vulnerable code (DomainNameValidator class) does not exist in this version - it was introduced in Django 5.1. Django 5.0.2 uses _simple_domain_name_validator which already validates against newlines via string.whitespace.", "justification": "code_not_present" } }, { "id": "CVE-2026-6873", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:5476710d-9018-59e7-9de9-91e4219d40f0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-6873 is fixed in version 5.0.2.post11+tuxcare of django." } }, { "id": "CVE-2026-8404", "affects": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ], "bom-ref": "urn:uuid:4323db6f-1dd3-555e-bbd3-9206059a5231", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-8404 is fixed in version 5.0.2.post11+tuxcare of django." } } ], "dependencies": [ { "ref": "pkg:pypi/django@5.0.2.post11+tuxcare" } ] }