{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:644744d1-f8b2-5639-ba2d-9664c6659c9c", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "django", "purl": "pkg:pypi/django@3.2.25.post11+tuxcare", "type": "library", "bom-ref": "pkg:pypi/django@3.2.25.post11+tuxcare", "version": "3.2.25.post11+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.post11+tuxcare" } ], "bom-ref": "urn:uuid:4af0e870-05ac-50f8-9294-ebd09c35e38f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-45115 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2021-45116", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:1e457bcb-4b0d-50df-8b5d-933f4fe60c9a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-45116 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2021-45452", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:e7a47ce4-e0ba-5b5e-a053-4082d37757df", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2021-45452 does not affect version 3.2.25.post11+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.post11+tuxcare" } ], "bom-ref": "urn:uuid:f2d02355-6f8e-59da-b88e-9b418c2aa5e4", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2022-22818 does not affect version 3.2.25.post11+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.post11+tuxcare" } ], "bom-ref": "urn:uuid:89bd09a1-34fa-5f07-ac42-3ea63711568c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-23833 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2022-28346", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:f9d902a0-12ae-5d29-b70e-e2730595e63d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-28346 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2022-28347", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:743db613-ff2e-51c6-b26b-4fae7b1853d3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-28347 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2022-34265", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:a5b8d26f-8486-581a-99f8-36294215da24", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-34265 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2022-36359", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:43ab084a-1548-54e8-97d4-0027f1ec5779", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-36359 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2022-41323", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:6e6e1311-f092-59ca-acb1-fa9d1b101c64", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-41323 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2023-23969", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:52a9fb3f-d7b0-5f60-ae9a-5e8afa3c8428", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-23969 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2023-24580", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:a03487ac-645e-51e2-af10-58a4fca3d53a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-24580 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2023-31047", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:9037b307-e39f-5baf-8b31-ea0a1479038b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-31047 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2023-36053", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:36a4182d-7c7e-54a1-8281-eb60aee33fdf", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-36053 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2023-41164", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:d35d0629-c562-5c18-a879-f71bac7d6cca", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-41164 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2023-43665", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:ea202898-2d62-5b5b-a39d-19ca38d2b6d9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-43665 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2023-46695", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:ba0ef35f-be8d-585f-b7b4-e9a27716144f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-46695 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2024-24680", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:49734d24-bc72-5f20-95e5-6f4545c0b3b6", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-24680 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2024-27351", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:60007f6e-c94a-5a79-9250-8f13d2b5ed5c", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2024-27351 does not affect version 3.2.25.post11+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.post11+tuxcare" } ], "bom-ref": "urn:uuid:1b1bf8b1-aa5f-538e-8293-21a33052a8d3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-38875 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2024-39329", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:a7e6c9e4-7e32-5aa4-be2b-760a5e2ab5f7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-39329 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2024-39330", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:bcd1badf-bbe6-5ce6-9a7a-8776eef6a4ed", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-39330 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2024-39614", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:24cec102-0e0d-5ee1-b8f2-ccb5b0fef89c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-39614 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2024-41989", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:3fcd45f9-44ba-576e-8863-0b0bbbab77f4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-41989 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2024-41990", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:d8c8a91d-04e3-5053-ad1e-5b582395a587", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-41990 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2024-41991", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:c09b4245-b0e6-587a-ae43-fde8295a0b6c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-41991 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2024-42005", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:c406e748-8d18-5950-aed4-ca6f8341dc07", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-42005 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2024-45230", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:cd5a1113-5e7e-53e1-a92f-f3a8eb0f3ef1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-45230 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2024-45231", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:109a579d-038a-5722-980c-f4032550f270", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-45231 is fixed in version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2024-53907", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:3b291093-30aa-5661-9dbb-84ac7e5bc001", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-53907 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2024-53908", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:1b67861f-9ba9-5ba0-a910-863ada45a5dd", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-53908 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2024-56374", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:1fec4149-097e-5758-9625-517301555a09", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-56374 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2025-13372", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:469b1417-2051-5401-bcc5-b4bfabd7fb27", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-13372 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2025-13473", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:6e0957cc-1f8f-5855-801d-f6a159d444e2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-13473 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2025-14550", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:898229b9-2464-50a2-8660-320f12833fa5", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-14550 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2025-26699", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:ff7c1c59-70e3-5b75-8dd9-87cb8e378c02", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-26699 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2025-27556", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:ad7f85b9-f2c4-5e9e-9b15-331ddd1d56b9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-27556 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2025-32873", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:877d4b56-49cd-51f0-b8a1-a8464af22302", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-32873 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2025-48432", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:4c56385d-a5bd-5218-9bda-7cf8589d194a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-48432 is fixed in version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2025-57833", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:7e1284cd-7154-5982-8235-c5924bf191d6", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-57833 is fixed in version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2025-59681", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:6191416f-d8e5-5ca8-bf56-f8516326e3b0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-59681 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2025-59682", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:d3e3b7bd-0fd7-5588-b49e-e9ea6c844ff1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-59682 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2025-64458", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:d681b161-d039-56ed-8cc2-9804b2028b11", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64458 is fixed in version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2025-64459", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:9cf23efe-ca8c-5abe-94b5-75691948f6d4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64459 is fixed in version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2025-64460", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:63edb15a-84be-507d-b08d-739d73b379fa", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-64460 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2026-1207", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:a1874381-ed7b-5696-83e6-41c346c441ca", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-1207 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2026-1285", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:db0c1621-7557-5fb9-bcf5-3583b6ee4fb5", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-1285 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2026-1287", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:aaa8f05f-b5c0-5e43-a647-01c9a48570c6", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-1287 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2026-1312", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:231cdc04-a240-5d7a-832f-e2157f89674c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-1312 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2026-15307", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:b1503d8b-088a-52fe-9bbc-fc1cc7a6ecc8", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15307 is fixed in version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2026-15830", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:cc1efe85-f027-56fe-b44e-cfc9e1433d9c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15830 is fixed in version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2026-25673", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:ca9c2694-ea69-59fd-801b-514d17965a11", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-25673 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2026-25674", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:a1bff9a9-6a79-50b9-86a8-14a10a06bc16", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-25674 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2026-33033", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:ea174978-f9a5-58af-bebe-08b436fbe922", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33033 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2026-33034", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:bba2b303-4fbf-545b-ba7b-092afe291137", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33034 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2026-3902", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:1014d0b6-773c-50fa-a30f-53076a028463", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-3902 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2026-4277", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:8798cb57-e51a-54ed-80b5-8e9878d735d2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-4277 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2026-4292", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:be5d837f-d5bd-5507-9522-46957a57b104", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-4292 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2026-48587", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:f477b80d-f4ae-5c4a-81ff-c1f95f6b0cd2", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48587 is fixed in version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2026-48588", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:01cbb6ea-dc0c-5a1f-83cb-591a81aea3ed", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48588 is fixed in version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2026-53877", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:04d15b09-724e-5ee3-ab3d-8b720c3e8385", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-53877 is fixed in version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2026-53878", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:96977371-e707-57fa-9159-f20d477d7f3b", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-53878 does not affect version 3.2.25.post11+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.post11+tuxcare" } ], "bom-ref": "urn:uuid:eb8c0151-f8af-50d0-8162-1e9c7aa99507", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-6873 is fixed in version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2026-8404", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:55287514-6091-544d-b9f4-83dbc0bfa945", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-8404 is fixed in version 3.2.25.post11+tuxcare of django." } } ], "dependencies": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ] }