{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:6240f89e-688d-5904-ad0b-801fa3bb8da9", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "django", "purl": "pkg:pypi/django@3.2.25.post10+tuxcare", "type": "library", "bom-ref": "pkg:pypi/django@3.2.25.post10+tuxcare", "version": "3.2.25.post10+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-2007-0404", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:4c8f90fa-e4fe-5ffe-a7d4-92fecfc153e3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2007-0404 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2007-0405", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:0b7beaae-e567-5f1d-aeb2-95f7c6d97696", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2007-0405 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2007-5712", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:db03245b-a94d-547a-b35f-8820fad42856", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2007-5712 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2008-2302", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:c7991a8b-297d-5075-8384-928f3d4fc377", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2008-2302 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2008-3909", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:92862eb5-c62c-5caa-9574-37146a610ef7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2008-3909 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2009-2659", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:f40ed412-29bb-502d-b1a7-a8599058f434", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2009-2659 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2009-3695", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:64fc12af-e1c9-55d8-82e6-85b18ca3c38d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2009-3695 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2010-3082", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:d35d7980-6e0b-5b26-a429-7c6fa9265f75", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2010-3082 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2010-4534", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:1e0f6da8-d2d2-59fe-900d-c6b3f8e4c2b0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2010-4534 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2010-4535", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:b76ad796-97e0-5db4-bc8d-90e65fd23f88", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2010-4535 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2011-0696", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:976a178c-15ee-52cf-b758-4b0293edfe19", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-0696 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2011-0697", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:3cc7e26a-ee63-55c1-9b7d-350345e6f71a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-0697 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2011-0698", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:d0c3d4e1-83c0-59d7-8722-c9e52e339530", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-0698 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2011-4136", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:4d46bd73-ca25-5761-a820-b8bc12c663db", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4136 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2011-4137", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:982dc912-15e6-5f19-90c8-b4b74c45f689", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4137 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2011-4138", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:d4cc5cbb-6a81-5b4d-af76-3ce72f4dc349", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4138 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2011-4139", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:1d0018ca-b9f5-5aae-8f4b-76982c25b651", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4139 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2011-4140", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:c88958e6-d336-5f7e-bd76-327f0a631d79", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4140 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2012-3442", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:8ded0cb2-0027-5c25-8569-1ddefab54d5e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2012-3442 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2012-3443", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:2c99b5d4-6a39-5582-9303-e2afc7b1430c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2012-3443 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2012-3444", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:7021baf6-c0a7-551c-8700-15d82516a781", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2012-3444 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2012-4520", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:9ee2c8b4-1232-5117-9a05-7215d03bf6fa", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2012-4520 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2013-0305", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:71bef88d-57df-58e2-8031-e4b41d1e69a1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-0305 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2013-0306", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:a0c1c630-3f40-5df7-8fd2-1003fff638a2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-0306 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2013-1443", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:098279d8-1498-58e4-8fef-dfc92f18a104", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-1443 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2013-1664", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:e6c9b089-298a-561d-bcd4-bd3effa7684a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-1664 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2013-1665", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:a97a869f-46f7-536b-958a-ba92b0ca579a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-1665 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2013-4249", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:6dab9925-81e6-5110-ac00-7edb4be44e6f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-4249 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2013-4315", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:6d06c1a4-60d9-5e4d-88a0-d281e5911e05", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-4315 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2013-6044", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:f4daad91-16ae-56ff-8cfa-1d5597e9ef27", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-6044 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2014-0472", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:5a5384c6-b194-5cc2-b32a-6ee873d2c5d5", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0472 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2014-0473", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:00b7ad67-8564-59fc-be98-5a19873f51ca", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0473 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2014-0474", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:505870a4-c572-5b4f-b3f4-fce05d2c912b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0474 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2014-0480", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:16bdb97a-9094-50dc-884a-26a800ccd493", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0480 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2014-0481", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:e8e8d621-c659-55b9-b31f-3cf5ca30bc8c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0481 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2014-0482", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:3a0fda7f-a5ba-502b-bfc1-21304b460d42", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0482 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2014-0483", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:78630dc3-3c7b-5b54-853f-525068049a2a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0483 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2014-1418", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:09ef5c71-86b2-5f82-832f-9feb4261ae77", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-1418 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2014-3730", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:31785c88-2a74-52dc-b36e-c2ae5f197883", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-3730 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2015-0219", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:e444ca61-1ffa-59a1-a6bc-185510b1f2a3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-0219 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2015-0220", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:6d90ed1c-25dc-5add-8776-ee1aacc3016c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-0220 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2015-0221", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:7464ffaf-80ba-53d1-89c6-4ef8da411213", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-0221 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2015-0222", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:77463de7-4857-597c-96dd-6e4421fea1ed", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-0222 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2015-2241", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:d6e5cf2e-e60f-57e0-aac4-cf8bbfc59061", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-2241 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2015-2316", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:11ce0fa7-5032-53f5-a1cd-54e030ec96a0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-2316 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2015-2317", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:c43cfecd-f5af-50d2-a0f0-3a028ae78ff9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-2317 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2015-3982", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:40862ad1-921d-5fd0-80db-1344def0e7da", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-3982 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2015-5143", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:589bbb6c-05de-5263-8a55-8c52216f315e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5143 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2015-5144", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:58f7928e-94fc-506b-a3ce-a470d5763b0e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5144 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2015-5145", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:cf0bf9dd-c0cb-5d58-9700-c335550eaa7a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5145 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2015-5963", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:2740d55d-c923-5059-80f0-c96cb3613198", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5963 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2015-5964", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:d73788a6-1673-5d32-b494-edb96e4e5dab", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5964 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2015-8213", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:34d4fcb4-9894-5a03-a0af-7af899863557", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-8213 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2016-2048", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:76a66ab2-b6c1-521a-8105-7aa4ebc83837", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-2048 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2016-2512", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:0c8e63a0-f3ed-58f7-8aee-ca920cd01813", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-2512 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2016-2513", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:49c57d77-5252-5f27-ade4-4e05395a2062", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-2513 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2016-6186", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:e5e51294-a20c-557f-8cff-d70f7f2e0865", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-6186 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2016-7401", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:2ea82d60-bde5-5ca9-a08b-ba755470875b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-7401 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2016-9013", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:c98f50c6-9ec8-52c3-93c3-07debe77dbfc", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-9013 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2016-9014", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:78ebaae3-ed09-5e10-8e39-2bdb5a155119", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-9014 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2017-12794", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:229e0013-23b6-506a-9841-46d3ba7e2fb8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2017-12794 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2017-7233", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:0f6ce52d-8290-5cab-b28a-487a7c58d591", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2017-7233 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2017-7234", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:a6f6123b-bf8c-58df-b929-b2ad3ec5a8eb", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2017-7234 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2018-14574", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:dcde3458-a2f6-5d17-b456-a3a025e941b2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-14574 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2018-16984", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:feca6f03-8a8f-5f2f-aabe-5bab72607a48", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-16984 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2018-6188", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:ebe002c2-0f48-51b5-84fb-854f0bcb9e17", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-6188 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2018-7536", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:9f190266-9758-530e-945b-63386d85d58c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-7536 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2018-7537", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:26003017-b23e-5ba8-b291-136e722b1d7c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-7537 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2019-11358", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:d678122b-b5cd-5c4c-9bd6-d1c6a63b2418", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-11358 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2019-12308", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:3a908f92-c458-578e-a064-0083961b0cfb", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-12308 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2019-12781", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:fde08d46-996c-5beb-834d-5c788a566972", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-12781 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2019-14232", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:4148800b-5885-5630-8372-83f5ee722155", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-14232 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2019-14233", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:c209b92b-0467-5e84-92b3-588ada39502e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-14233 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2019-14234", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:8c473c84-7737-5441-ae34-9d7e225f38af", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-14234 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2019-14235", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:6c65942e-3995-5587-8d9a-c757e157e8f6", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-14235 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2019-19118", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:d038c6fc-5a95-5566-ba1d-de367b532493", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-19118 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2019-19844", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:af9f9033-18fb-51e2-bc39-77d254d940fa", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-19844 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2019-3498", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:28eb2217-aa5c-5155-9ea2-255bd29ff1eb", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-3498 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2019-6975", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:ce75257f-2984-59ba-9281-08c631b3ee16", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-6975 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2020-13254", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:16cb2fd5-0d53-5a23-8c9f-a7d53b739e39", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-13254 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2020-13596", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:ee1e932b-937c-5601-aa82-1b61767935c3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-13596 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2020-24583", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:45b112c9-5848-5d3b-8dd2-fe159acf1cb3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-24583 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2020-24584", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:86bb1177-7a16-5c9a-91d7-ebfc8de5c2cc", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-24584 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2020-7471", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:7f2ab2fc-71b2-5c33-b807-2a29089b0d47", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-7471 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2020-9402", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:a93d5f8f-f977-5220-9cbc-37fc73d28c8e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-9402 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2021-28658", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:ea329f92-5038-5f23-920d-3f3a1df8ffe4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-28658 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2021-31542", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:0dbe412a-d3c4-529f-bde9-98ff24cc6134", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-31542 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2021-32052", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:cfbc9eaf-75b3-5c08-be8f-71f428ec6a58", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-32052 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2021-3281", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:aa81e996-74e3-57f9-b374-c5e508d58465", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-3281 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2021-33203", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:a548bcfd-ac71-51e5-9e04-98c269058a1e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-33203 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2021-33571", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:86e6184c-d91b-5eb1-a20c-8561f7a69b89", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-33571 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2021-35042", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:70863afc-da1f-5070-97a7-e3ee08c441d1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-35042 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2021-44420", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:965368b6-38df-5ab0-afc0-b50ab1be1635", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-44420 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2021-45115", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:38536073-2637-53a3-9012-b7afeaceb66f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-45115 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2021-45116", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:d2fb8305-f0a4-5fc9-93a1-b1359083fda9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-45116 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2021-45452", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:98945c6a-b6b5-5a20-a8bb-7624f8a57def", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2021-45452 does not affect version 3.2.25.post10+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.post10+tuxcare" } ], "bom-ref": "urn:uuid:92ca2bf6-c301-5cb0-982b-bd76e514ce07", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2022-22818 does not affect version 3.2.25.post10+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.post10+tuxcare" } ], "bom-ref": "urn:uuid:c78220db-d2a6-5b3c-973f-f8254a09f44d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-23833 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2022-28346", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:4709cb9c-3d4a-5574-bf18-5ca4b4988b9f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-28346 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2022-28347", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:36c9e698-7093-5259-ad0d-263abc0206d4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-28347 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2022-34265", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:f3c479d4-ee08-5a88-bdf2-3a6e41a4060c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-34265 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2022-36359", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:dff93f16-a047-5fef-a9cf-c2e3fce37680", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-36359 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2022-41323", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:b1484f69-9860-5b1f-ae25-69940c02a998", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-41323 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2023-23969", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:6213e561-2d86-5ce0-b7c2-e29646b2b5fc", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-23969 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2023-24580", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:22fefd76-5887-5ed9-b74c-5a4afbd64f8e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-24580 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2023-31047", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:9d1c8534-c68b-54e3-a488-98a1aae26be7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-31047 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2023-36053", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:048012c0-e80a-5430-a725-6eab7a98849d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-36053 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2023-41164", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:a9a6f3d3-d537-532d-9708-7d2559827848", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-41164 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2023-43665", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:9d9301eb-6a8c-5b88-a864-494dbdf50f31", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-43665 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2023-46695", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:62b7009a-f8d0-5d96-ab89-4c9e6607b260", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-46695 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2024-24680", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:f9a08f2e-dfea-5024-8af7-13f95d0670fb", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-24680 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2024-27351", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:fa417bbe-4d56-59f8-9ccb-1cdf61ef8807", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2024-27351 does not affect version 3.2.25.post10+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.post10+tuxcare" } ], "bom-ref": "urn:uuid:8abdc39a-3c7e-5f04-a4a5-efcd5774b110", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-38875 affects version 3.2.25.post10+tuxcare of django, and is fixed in 3.2.25.post17+tuxcare." } }, { "id": "CVE-2024-39329", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:11fd49ce-8c6a-57dd-b43a-c86e91fc659b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39329 is already fixed in version 3.2.25.post10+tuxcare of django. CVE-2024-39329 already fixed on tuxcare-current/3.2.25 by cf29797b67 (inside the CVE-2025-13473 backport), released in 3.2.25.post14+tuxcare; authenticate timing equal for unusable-password users on post17." } }, { "id": "CVE-2024-39330", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:f7d6f5b9-4c31-5382-a857-abb5234154f0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-39330 affects version 3.2.25.post10+tuxcare of django, and is fixed in 3.2.25.post16+tuxcare." } }, { "id": "CVE-2024-39614", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:c0615d58-be5d-503c-995c-4452bfe18f81", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-39614 affects version 3.2.25.post10+tuxcare of django, and is fixed in 3.2.25.post16+tuxcare." } }, { "id": "CVE-2024-41989", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:bdecfd88-3c30-5b85-8d4e-c54d53a566b6", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2024-41989 does not affect version 3.2.25.post10+tuxcare of django. Django 3.2.25 floatformat() parses repr(text): str/Decimal input yields quotes, parsing fails and the value goes through float() with a bounded exponent; upstream test inputs run in 0.000s. The expensive path needs an object with a numeric __repr__, not attacker-supplied. See PYELSCVE-3148 / django!68.", "justification": "code_not_reachable" } }, { "id": "CVE-2024-41990", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:df32898b-074c-5f9f-b211-a25c9f7e0784", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-41990 affects version 3.2.25.post10+tuxcare of django, and is fixed in 3.2.25.post17+tuxcare." } }, { "id": "CVE-2024-41991", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:e246af51-1226-5659-9685-b0c03ebe590c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-41991 affects version 3.2.25.post10+tuxcare of django, and is fixed in 3.2.25.post17+tuxcare." } }, { "id": "CVE-2024-42005", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:ca77bbfc-358b-5bb8-aba6-76ecba24eeb8", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2024-42005 does not affect version 3.2.25.post10+tuxcare of django. Django 3.2.25: names passed to QuerySet.values()/values_list() never become SQL aliases on 3.2 (alias grouping arrived in 4.2, django 04518e310d); 11 query shapes injected 7/11 on 4.2 pre-fix and 0/11 on 3.2.25 (sqlite). See PYELSCVE-3148 / django!68.", "justification": "code_not_reachable" } }, { "id": "CVE-2024-45230", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:bc9c3989-218e-55cd-af76-55980850c75f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-45230 affects version 3.2.25.post10+tuxcare of django, and is fixed in 3.2.25.post17+tuxcare." } }, { "id": "CVE-2024-45231", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:21567b0a-c122-52ff-8588-9d1bbf2d8f68", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-45231 is fixed in version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2024-53907", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:9a70966b-e587-5de8-856b-3db1354f4930", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-53907 affects version 3.2.25.post10+tuxcare of django, and is fixed in 3.2.25.post17+tuxcare." } }, { "id": "CVE-2024-53908", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:75ae9491-8bbe-5fb2-850c-515cf64b91a5", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-53908 affects version 3.2.25.post10+tuxcare of django, and is fixed in 3.2.25.post18+tuxcare." } }, { "id": "CVE-2024-56374", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:a846fb1b-46aa-597b-acf1-8957ff7cec38", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-56374 affects version 3.2.25.post10+tuxcare of django, and is fixed in 3.2.25.post16+tuxcare." } }, { "id": "CVE-2025-13372", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:88f37535-7568-5f9c-b1cf-b098a0629f35", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-13372 affects version 3.2.25.post10+tuxcare of django, and is fixed in 3.2.25.post14+tuxcare." } }, { "id": "CVE-2025-13473", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:9c2bfa7e-45ca-5892-b6aa-defeb443122e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-13473 affects version 3.2.25.post10+tuxcare of django, and is fixed in 3.2.25.post14+tuxcare." } }, { "id": "CVE-2025-14550", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:34a98b21-5aeb-50fa-a082-d8160cac636f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-14550 affects version 3.2.25.post10+tuxcare of django, and is fixed in 3.2.25.post13+tuxcare." } }, { "id": "CVE-2025-26699", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:db7603fd-0ba4-50f7-a021-7c1c59e4e3a8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-26699 affects version 3.2.25.post10+tuxcare of django, and is fixed in 3.2.25.post16+tuxcare." } }, { "id": "CVE-2025-27556", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:87323283-f0cb-5232-a6db-56a83530ff7f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-27556 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2025-32873", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:463ac2cf-26e5-55dd-a608-45116dc3a68d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-32873 affects version 3.2.25.post10+tuxcare of django, and is fixed in 3.2.25.post16+tuxcare." } }, { "id": "CVE-2025-48432", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:6d3db12d-85dc-5110-b5ce-a4e2a11974d6", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-48432 is fixed in version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2025-57833", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:cd989861-31c4-5a50-a1e4-bec953b94230", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-57833 is fixed in version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2025-59681", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:220e1454-4eaa-5bae-896d-641a255c71fb", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-59681 is already fixed in version 3.2.25.post10+tuxcare of django. CVE-2025-59681 already fixed on tuxcare-current/3.2.25 by ec740f90ef, released in 3.2.25.post4+tuxcare; all four of annotate/alias/aggregate/extra reject alias with '#' on 3.2.25.post17." } }, { "id": "CVE-2025-59682", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:4ae65401-f607-5a29-ba1b-ac9773c0d59b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-59682 affects version 3.2.25.post10+tuxcare of django, and is fixed in 3.2.25.post16+tuxcare." } }, { "id": "CVE-2025-64458", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:19068fd2-f131-51f9-83a7-5e0991e94b1c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64458 is fixed in version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2025-64459", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:28a63d7d-fb1e-5694-83ba-f237603fdaa5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64459 is fixed in version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2025-64460", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:235d93c9-1d9a-57d5-bfa0-aeab4d0b62b4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-64460 affects version 3.2.25.post10+tuxcare of django, and is fixed in 3.2.25.post13+tuxcare." } }, { "id": "CVE-2026-108147", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:eff55765-d89b-5396-83b3-cff70d8ebbe4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-108147 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2026-111211", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:4f16ef8d-58c5-54df-8db5-20a0fbebc567", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-111211 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2026-111362", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:f8d1739c-2789-57e5-b6bd-e9b8c3a632eb", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-111362 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2026-113593", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:65999f03-0f25-5830-93bb-27b9cb011607", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-113593 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2026-113733", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:97231c81-519b-57f3-8775-96cfee1979d3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-113733 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2026-114582", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:8b55b15e-332b-5b39-895a-33f8ac91791a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-114582 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2026-1207", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:7b0e0842-2b2d-53c1-9daf-cdcbc19cb481", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-1207 affects version 3.2.25.post10+tuxcare of django, and is fixed in 3.2.25.post14+tuxcare." } }, { "id": "CVE-2026-1285", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:27cd5c23-b800-5515-839a-009be0c9026e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-1285 affects version 3.2.25.post10+tuxcare of django, and is fixed in 3.2.25.post13+tuxcare." } }, { "id": "CVE-2026-1287", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:7c2345cf-97d2-5abd-afa3-5f940875570a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-1287 affects version 3.2.25.post10+tuxcare of django, and is fixed in 3.2.25.post14+tuxcare." } }, { "id": "CVE-2026-1312", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:e7a4e3b4-5044-5bee-aff7-79ef4160fe66", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-1312 affects version 3.2.25.post10+tuxcare of django, and is fixed in 3.2.25.post15+tuxcare." } }, { "id": "CVE-2026-15307", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:141694df-8504-5ab9-bca8-f20690528d02", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15307 is fixed in version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2026-15830", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:9a9436e6-8275-5281-9399-5e17c260d11c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15830 is fixed in version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2026-25673", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:79765223-ee1d-5d24-a927-9941693b00fd", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-25673 affects version 3.2.25.post10+tuxcare of django, and is fixed in 3.2.25.post14+tuxcare." } }, { "id": "CVE-2026-25674", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:077a25ac-19aa-5432-8e5c-e40e6cebc44c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-25674 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2026-33033", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:56e5a9c2-4454-5ffe-a1c8-65d4ffe56729", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33033 affects version 3.2.25.post10+tuxcare of django, and is fixed in 3.2.25.post14+tuxcare." } }, { "id": "CVE-2026-33034", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:0848eceb-ee88-52e0-9bcc-99cc7e61d542", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33034 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2026-35192", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:c4518fa5-24d6-5588-ac49-b7d04fa189ef", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-35192 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2026-35193", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:fa5b1ff3-d5dc-504b-a595-531296b4cf37", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-35193 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2026-3902", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:93b729c8-6552-52ac-be26-17ed357aa9a2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-3902 affects version 3.2.25.post10+tuxcare of django, and is fixed in 3.2.25.post14+tuxcare." } }, { "id": "CVE-2026-4277", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:2629a60e-0ca4-5250-b909-18965a6c7526", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-4277 affects version 3.2.25.post10+tuxcare of django, and is fixed in 3.2.25.post14+tuxcare." } }, { "id": "CVE-2026-4292", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:00c08db9-3eea-5333-97a6-80b1bf5e0c1f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-4292 affects version 3.2.25.post10+tuxcare of django, and is fixed in 3.2.25.post14+tuxcare." } }, { "id": "CVE-2026-48587", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:e9173d25-3329-5e9f-b5f6-8e45164058b9", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48587 is fixed in version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2026-48588", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:6255ada9-cb2f-5898-8a80-e22ef6dd7174", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48588 is fixed in version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2026-53877", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:edf2fbb5-70b4-5f4a-b573-a96c348946f8", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-53877 is fixed in version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2026-53878", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:e07dfe2e-5291-5216-a06c-65603e7a976c", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-53878 does not affect version 3.2.25.post10+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-5766", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:f5ebfddc-997b-515b-af17-719d2af79600", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-5766 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2026-6873", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:3f753436-64c4-5a9b-809e-56523e915786", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-6873 is fixed in version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2026-6907", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:1fd1d2d1-9071-5ecc-bf1a-18898c23cbda", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-6907 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2026-7666", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:6b7599ec-0c20-580b-ab66-ab91ba2b58a9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-7666 affects version 3.2.25.post10+tuxcare of django." } }, { "id": "CVE-2026-8404", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ], "bom-ref": "urn:uuid:b415c382-9e29-5231-bc98-9a1a2cf6c3ce", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-8404 is fixed in version 3.2.25.post10+tuxcare of django." } } ], "dependencies": [ { "ref": "pkg:pypi/django@3.2.25.post10+tuxcare" } ] }