{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:8b8209df-8971-5ccd-8360-2bdbbe304160", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "django", "purl": "pkg:pypi/django@3.2.25.post12+tuxcare", "type": "library", "bom-ref": "pkg:pypi/django@3.2.25.post12+tuxcare", "version": "3.2.25.post12+tuxcare", "pedigree": { "ancestors": [ { "name": "django", "purl": "pkg:pypi/django@3.2.25", "type": "library", "version": "3.2.25" } ] }, "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2021-45115", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:55f664df-8bbc-5278-a091-8ee778eef338", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-45115 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2021-45116", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:8b01ce4d-ac80-5d3b-853c-a1e55f45614e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-45116 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2021-45452", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:4e5434f2-1cf6-5f2f-a94a-10924ef95bc2", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2021-45452 does not affect version 3.2.25.post12+tuxcare of django. not_affected \u2014 The target (Django 3.2.25) is not affected by CVE-2021-45452. The upstream fix from Django 3.2.11 (commit 8d2f7cff76) was already present in the release that TuxCare onboarded. All three fix components are present in django/core/files/storage.py: (1) backslash normalization before path validation in get_available_name() and generate_filename(), (2) relative path enforcement via os.path.relpath(...", "justification": "code_not_present" } }, { "id": "CVE-2022-22818", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:fb76856a-f1f1-53e2-886d-15aeee7bd535", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2022-22818 does not affect version 3.2.25.post12+tuxcare of django. not_affected \u2014 The target Django 3.2.25.post12+tuxcare is NOT affected by CVE-2022-22818. The vulnerability (unescaped output in the {% debug %} template tag leading to XSS) was fixed in upstream Django 3.2.12. The target version 3.2.25 already contains the complete fix from commit 1a1e8278c4, which HTML-escapes all debug output via the escape() function. This fix was authored by upstream Django developers an...", "justification": "code_not_present" } }, { "id": "CVE-2022-23833", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:e1bfb061-3aef-5f6d-9cb0-1558ce756716", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-23833 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2022-28346", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:bd2af96a-a7cb-5354-8af0-523fa9bba88c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-28346 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2022-28347", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:0e474ed8-5511-5d5b-9651-283e51278633", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-28347 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2022-34265", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:85c0ee7e-5ecb-5d38-a311-d46992f42b6a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-34265 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2022-36359", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:4ebf77b0-d842-5d35-95fa-0bb0828dba9c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-36359 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2022-41323", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:481629f2-9ae2-5ca1-abfe-870be3e8d8e4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-41323 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2023-23969", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:5fba8065-d1cb-5797-a30b-f668068411a3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-23969 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2023-24580", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:cccc274c-418b-5470-b0c0-7f4780e98467", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-24580 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2023-31047", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:f8667fd2-d4d8-57e4-9303-e3dfe0c3de96", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-31047 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2023-36053", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:0937f5d2-8c02-58a6-8142-bc75118fb9a5", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-36053 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2023-41164", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:af619632-0f8f-5492-8ac4-3c7aae751ccd", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-41164 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2023-43665", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:4163f230-06a9-501a-a1a9-e8534ee3a1a5", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-43665 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2023-46695", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:47b1d2b1-0344-5989-a813-ea5a4ff5981b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-46695 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2024-24680", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:46d89d08-a717-5eab-8cad-c06da2852d71", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-24680 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2024-27351", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:849c3f83-9e02-5d00-8243-62b74b288618", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2024-27351 does not affect version 3.2.25.post12+tuxcare of django. not_affected \u2014 CVE-2024-27351 is not present in Django 3.2.25.post12+tuxcare. The vulnerable regular expression pattern that caused catastrophic backtracking has been replaced by a secure WordsRegex class implementation. This fix was authored by upstream Django maintainer Shai Berger (shai@platonix.com) in commit 072963e4c4d0b3a7a8c5412bc0c7d27d1a9c3521 and was included in the upstream Django 3.2.25 release b...", "justification": "code_not_present" } }, { "id": "CVE-2024-38875", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:042027c2-858d-55f0-b563-1336da334152", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-38875 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2024-39329", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:c31f7603-afda-5bbe-bc20-8a06fee75ba2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-39329 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2024-39330", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:cae736ea-088f-5903-804c-0fb66ab6c5b7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-39330 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2024-39614", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:ad4df8f2-8256-5233-9422-ba46f3e01bb7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-39614 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2024-41989", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:94d78348-2b81-5285-ac21-bde844a5ad68", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-41989 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2024-41990", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:e6c061aa-5f55-5470-962a-5faab3e59ee4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-41990 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2024-41991", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:fe3d651a-e873-54db-95af-edb1d01f597c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-41991 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2024-42005", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:cbcf3a2e-bbdc-5698-a3a5-b0e3ac4b1116", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-42005 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2024-45230", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:00e36126-e505-5d35-a3b9-1d8d6c4abd84", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-45230 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2024-45231", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:9c190a53-aa81-5c3b-9c3d-4d661410db1f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-45231 is fixed in version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2024-53907", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:bec58042-f945-5227-8662-b3d01b4b1c03", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-53907 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2024-53908", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:333fc761-34fc-5bd0-a6fc-51bd0dff1a7f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-53908 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2024-56374", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:534949de-021c-53e0-816e-ae36dcfa87a0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-56374 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2025-13372", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:70de0b72-8a2c-5d17-a287-e088f965e4e2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-13372 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2025-13473", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:442b6f79-d41e-5b9a-a77d-8004bce9ae9d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-13473 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2025-14550", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:a03ced24-38cd-53ef-851e-cc623a159ba1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-14550 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2025-26699", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:335a8f38-e19b-5f18-b0b1-0cc03159d49b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-26699 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2025-27556", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:b1545ad1-53eb-5135-857c-fca4493ba12c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-27556 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2025-32873", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:17aa2ea6-6ff5-55b6-ab35-8fede897b6c7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-32873 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2025-48432", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:d96874aa-4a1e-527a-9c90-08ff006de516", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-48432 is fixed in version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2025-57833", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:2703f238-d9c3-54f7-a5ed-d31e9f0713cc", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-57833 is fixed in version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2025-59681", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:ca6ce961-eda6-5f1d-b561-2f3ed68bc7ce", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-59681 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2025-59682", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:88e6cd3a-2b27-5108-ae2d-4a77a3c5432d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-59682 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2025-64458", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:9abe2cf2-5cad-50d4-b44a-b3967c84e6cb", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64458 is fixed in version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2025-64459", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:0157bc49-f413-59cd-9b3f-f6a85f0b2b36", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64459 is fixed in version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2025-64460", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:24ee3878-1153-5e2a-baf4-c055ce30cf58", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-64460 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2026-1207", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:e9736b0c-86d2-559d-b9dd-94fc089536a7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-1207 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2026-1285", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:80e33677-6595-5321-9347-88e02870de22", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-1285 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2026-1287", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:338a1309-5f0a-5497-8050-9b8bb6ceb4b9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-1287 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2026-1312", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:c182b13d-3485-5dfd-8c71-1337c0802a56", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-1312 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2026-15307", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:b8336c69-3d07-5b90-b855-afbabfff29c2", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15307 is fixed in version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2026-15830", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:d6933bd5-df92-51c5-95a8-70a1fecf7702", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15830 is fixed in version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2026-25673", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:d1836b9a-7de5-506a-ad2e-ea99d8b3246d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-25673 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2026-25674", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:eee06e3a-43ec-5610-8569-7b4af2dea3d5", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-25674 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2026-33033", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:a8f6d3a2-3364-5576-a390-727f692c7993", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33033 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2026-33034", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:0add1068-25c3-5b0b-8664-def42f8a6340", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33034 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2026-3902", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:a0a35d78-bf24-58dd-9a8b-806643e26eda", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-3902 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2026-4277", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:81d759fb-e5f0-5c03-bc71-2992bfce31d0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-4277 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2026-4292", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:a2ba2e12-d069-594a-b279-6bb7ff63b7d6", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-4292 affects version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2026-48587", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:a370dffc-ff57-5dc6-87e9-7da24564e818", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48587 is fixed in version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2026-48588", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:df857fca-3b78-59ef-89a6-6e3b4a140b1c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48588 is fixed in version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2026-53877", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:828688ed-6ca3-5a8f-8586-89d98e73444a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-53877 is fixed in version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2026-53878", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:3b004cbe-736f-540b-bb16-7da94e3021b6", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-53878 does not affect version 3.2.25.post12+tuxcare of django. not_affected \u2014 Django 3.2.25 is not affected by CVE-2026-53878. The CVE concerns `DomainNameValidator` (introduced in Django 5.x/6.x) which does not prohibit newlines in domain names. Django 3.2.25 lacks this class entirely. The existing domain validators (`_simple_domain_name_validator` in sites/models.py, `EmailValidator.validate_domain_part()` in core/validators.py) already prohibit newlines either explici...", "justification": "protected_at_runtime" } }, { "id": "CVE-2026-6873", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:101bd9ec-3130-51c6-9e1b-38f646cc35a7", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-6873 is fixed in version 3.2.25.post12+tuxcare of django." } }, { "id": "CVE-2026-8404", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ], "bom-ref": "urn:uuid:1db5f08f-939b-56c4-846e-2408b7411918", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-8404 is fixed in version 3.2.25.post12+tuxcare of django." } } ], "dependencies": [ { "ref": "pkg:pypi/django@3.2.25.post12+tuxcare" } ] }