{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:0b5990f6-5abe-53b0-8869-2ab828f69ccf", "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-2007-0404", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:58f96cb9-dc40-553a-bfac-a47bcc65aff8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2007-0404 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2007-0405", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:63e52c15-52b7-5c2c-846a-0a074c724506", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2007-0405 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2007-5712", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:fccd4386-6131-5892-a6b4-5c0af228dc34", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2007-5712 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2008-2302", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:9ccb4710-cdbb-5e48-89be-ce33b35531ed", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2008-2302 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2008-3909", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:4588b2e4-1fd1-5ba7-ad18-05779db6fbce", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2008-3909 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2009-2659", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:4c38e8ad-c25e-5a4f-91ce-27e907985e8a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2009-2659 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2009-3695", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:f661890b-9955-5951-b048-49b14c7a2891", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2009-3695 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2010-3082", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:f55f2f26-86f9-56a3-9b57-ebf2ea25cc34", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2010-3082 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2010-4534", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:356a7581-31f5-5664-affe-05cb9b0caf0a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2010-4534 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2010-4535", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:da49593c-ef89-5ca6-b77a-c77d71918df1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2010-4535 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2011-0696", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:206338b0-f17e-5c1c-8c24-8ab5080d89fa", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-0696 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2011-0697", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:e3c859fd-8727-51f5-bc02-919bb560a9a0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-0697 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2011-0698", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:ead60c66-b39a-53c8-9e41-e655967fb0e9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-0698 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2011-4136", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:f3078690-31ce-5e2a-864e-9377ad9f18e3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4136 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2011-4137", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:1e3123b6-f6eb-56c6-9ce0-899726a07a83", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4137 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2011-4138", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:137d8f76-ea90-5062-b379-3a598192454e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4138 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2011-4139", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:a44a8a1d-b463-5659-b4b0-95eef426a860", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4139 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2011-4140", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:ba6da86c-6232-5528-aabc-f743a56e35f6", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4140 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2012-3442", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:0c3d3308-15c8-5ba1-a616-5fe65bcad0d3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2012-3442 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2012-3443", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:448a1f5b-4adc-5364-8d38-5d2f69d68927", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2012-3443 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2012-3444", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:f7227b3d-f66e-51ee-92d4-06cc3e4e83e0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2012-3444 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2012-4520", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:6a2159df-2fee-54d1-9158-f4c6a6d20f84", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2012-4520 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2013-0305", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:39063177-0a89-5061-b6d0-2e90d8d2b5ee", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-0305 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2013-0306", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:98c79c92-7bce-5841-84cd-415ba24b6707", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-0306 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2013-1443", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:2f845c9e-cd70-5681-8c93-cf5bb6535835", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-1443 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2013-1664", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:e628d049-5a0b-56a5-84e6-f1260efbceeb", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-1664 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2013-1665", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:ac522ebc-1c31-5c4b-a0f1-fed082348934", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-1665 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2013-4249", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:e8d1a823-dd18-5f84-8175-d4e4dd3a697e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-4249 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2013-4315", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:fc9d5a4a-b41a-55c5-a0ec-6c5e9ef03a46", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-4315 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2013-6044", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:5f8b2678-4151-5944-85e6-e551f88d8769", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-6044 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2014-0472", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:70ad4c85-d214-5673-bfe7-9af9db08f26a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0472 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2014-0473", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:66cace10-6ef1-5a17-b758-307b3bad5094", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0473 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2014-0474", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:81d9e1da-23ee-540f-95a7-78f0bd771f11", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0474 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2014-0480", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:a56d26d8-084e-5e7c-b1e7-eff4ff8ecc49", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0480 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2014-0481", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:5b7f956b-e4ae-52e0-aa75-87c099591eba", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0481 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2014-0482", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:c80dce56-ddde-5e24-9b91-056a7932b90e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0482 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2014-0483", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:7af225e3-f58d-5a80-b403-09d5db1266db", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0483 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2014-1418", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:3e11b683-7478-53b8-a8fc-ba658d403090", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-1418 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2014-3730", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:ea36f642-3993-5759-949b-5fde5d8a90a1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-3730 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2015-0219", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:aa95d01c-f2ef-5b85-ac32-d3133fc76995", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-0219 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2015-0220", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:80c8f0f1-77ab-5ff1-87b8-4a0ed0f909c3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-0220 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2015-0221", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:671902df-14e6-5ac3-9772-48b640294915", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-0221 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2015-0222", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:e0a5d366-3fec-5e41-bf94-9bcbb6b6bc56", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-0222 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2015-2241", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:42d0d504-6fc2-5558-8bd0-2a276e0bfa47", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-2241 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2015-2316", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:01c2d0a1-bd26-5bfd-ad07-09a1dc17546b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-2316 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2015-2317", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:d4cd1cd6-a40e-5c8b-82df-52c9870ce56c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-2317 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2015-3982", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:4d398a98-82f7-5489-b779-32fdf9b6ac08", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-3982 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2015-5143", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:fd12a2d5-4798-55d1-a3a9-c33487296538", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5143 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2015-5144", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:4e601fd2-4c7b-5037-bb7d-3af8501044dd", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5144 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2015-5145", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:dc0bc6e6-2c02-5219-8a2b-faa1b2c1ec70", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5145 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2015-5963", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:e33ac9b7-fa03-547e-ad80-924c91437753", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5963 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2015-5964", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:7add5f2c-c763-516b-847f-b7cae688cd4a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5964 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2015-8213", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:dbf35668-20bc-5179-a990-c0bdd6c68e9e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-8213 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2016-2048", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:bc678161-a45c-5752-b98a-58deca08338c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-2048 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2016-2512", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:61501fbe-138f-5d83-924d-14b759d43559", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-2512 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2016-2513", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:2b3303e5-af95-5782-b441-ccb478622c6e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-2513 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2016-6186", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:914e29be-e79b-5dad-948b-492d31a78e1e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-6186 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2016-7401", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:75cfaa0a-30bd-53f0-ae9a-a64bd847f2af", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-7401 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2016-9013", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:07e518ef-a245-5927-8189-837fa9eff596", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-9013 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2016-9014", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:a3c5fc95-a0d1-516b-bda5-f61cf78312ea", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-9014 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2017-12794", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:518119e3-b8ad-508e-acf5-be334a6b8891", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2017-12794 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2017-7233", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:d4656662-6317-5115-b32f-29bad2620b63", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2017-7233 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2017-7234", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:ce4a2882-991e-580b-a428-37e338d736ca", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2017-7234 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2018-14574", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:de9b9d39-f5d8-55ca-b70c-a45fb05a6e2e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-14574 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2018-16984", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:e37c2fa5-9518-50af-b4d0-b3df9c7cf5ca", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-16984 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2018-6188", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:6e8e38ac-3de9-5adf-a57d-ce64d5d3a6c3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-6188 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2018-7536", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:bd8a4c30-c420-58e6-9f8c-bd3d511f8ff7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-7536 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2018-7537", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:b4d1d5d4-0eb3-5f91-82cd-2c608181e715", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-7537 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2019-11358", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:57ff828e-52f3-5692-bde9-c1747297a9bf", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-11358 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2019-12308", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:b95878a4-f78f-5a3a-923b-284fe2e937b6", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-12308 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2019-12781", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:c2b7498b-e1e6-565f-9d4a-aa36fc791267", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-12781 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2019-14232", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:e760d7cc-b979-5863-97c0-016910f196d3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-14232 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2019-14233", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:2ae90c7f-7565-575d-898f-4b6f2515bb46", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-14233 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2019-14234", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:3519a98a-3899-5641-83de-054dc5ee003b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-14234 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2019-14235", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:b6a41d33-d1c1-56af-b0c9-583e8c38bff4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-14235 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2019-19118", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:f5089af9-a59c-592f-831a-64e3d01eb862", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-19118 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2019-19844", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:ad011b1d-19a7-5a4c-a4e1-54de99da04a5", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-19844 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2019-3498", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:35698ac5-415b-59bc-850d-104f66d1d2c2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-3498 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2019-6975", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:cb77bd42-124a-5fbd-84eb-be962c39ea52", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-6975 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2020-13254", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:a461b750-081e-5656-b00e-b31610102bf5", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-13254 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2020-13596", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:1c41faaa-1f19-5e08-9cd3-c9420f107cf9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-13596 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2020-24583", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:82fa2290-d7e8-558e-88ff-7dad2f6af3a0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-24583 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2020-24584", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:50f43f62-5abe-52a4-afa5-6ab983f6a514", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-24584 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2020-7471", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:4d261cd3-b7c9-53ba-9090-5638d097c5d5", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-7471 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2020-9402", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:8218442e-db40-5a26-bed9-ca21837e7849", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-9402 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2021-28658", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:95babe9f-34e4-54ec-a815-9de550cdc9e2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-28658 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2021-31542", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:bdc28a12-9d6e-5942-8def-c13567fe9fe8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-31542 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2021-32052", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:68a277ff-8498-5653-93fd-c9c2c659b8c3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-32052 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2021-3281", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:1d6751aa-d1ab-5784-8e7a-9027922010df", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-3281 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2021-33203", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:c996355d-4b3b-5a88-9f68-b18fc6c5f6b5", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-33203 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2021-33571", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:a824d3dc-6475-5d03-999b-881ee9d44a87", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-33571 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2021-35042", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:19620649-416c-54ac-9e6d-4ad9c752a7f3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-35042 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2021-44420", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:7e255d54-9712-5f5b-816b-37066e183f5c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-44420 affects version 3.2.25.post11+tuxcare of django." } }, { "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, and is fixed in 3.2.25.post17+tuxcare." } }, { "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": "resolved", "detail": "Vulnerability CVE-2024-39329 is already fixed in version 3.2.25.post11+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.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, and is fixed in 3.2.25.post16+tuxcare." } }, { "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, and is fixed in 3.2.25.post16+tuxcare." } }, { "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": "not_affected", "detail": "Vulnerability CVE-2024-41989 does not affect version 3.2.25.post11+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.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, and is fixed in 3.2.25.post17+tuxcare." } }, { "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, and is fixed in 3.2.25.post17+tuxcare." } }, { "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": "not_affected", "detail": "Vulnerability CVE-2024-42005 does not affect version 3.2.25.post11+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.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, and is fixed in 3.2.25.post17+tuxcare." } }, { "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, and is fixed in 3.2.25.post17+tuxcare." } }, { "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, and is fixed in 3.2.25.post18+tuxcare." } }, { "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, and is fixed in 3.2.25.post16+tuxcare." } }, { "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, and is fixed in 3.2.25.post14+tuxcare." } }, { "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, and is fixed in 3.2.25.post14+tuxcare." } }, { "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, and is fixed in 3.2.25.post13+tuxcare." } }, { "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, and is fixed in 3.2.25.post16+tuxcare." } }, { "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, and is fixed in 3.2.25.post16+tuxcare." } }, { "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": "resolved", "detail": "Vulnerability CVE-2025-59681 is already fixed in version 3.2.25.post11+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.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, and is fixed in 3.2.25.post16+tuxcare." } }, { "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, and is fixed in 3.2.25.post13+tuxcare." } }, { "id": "CVE-2026-108147", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:f4e2cd12-c21b-53b7-9b48-b406cda6e3f6", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-108147 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2026-111211", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:92848875-437b-52ed-8e38-8c79889a95f7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-111211 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2026-111362", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:354e2688-9032-5c0d-a7b0-44e530b51178", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-111362 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2026-113593", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:69672896-e4b0-5027-9ca3-0d988a9097d6", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-113593 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2026-113733", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:4f3f7e3f-2329-5032-8d10-9f914ac4633d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-113733 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2026-114582", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:bfd51a6e-fa4d-5800-ab48-2abb4e54ccbc", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-114582 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, and is fixed in 3.2.25.post14+tuxcare." } }, { "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, and is fixed in 3.2.25.post13+tuxcare." } }, { "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, and is fixed in 3.2.25.post14+tuxcare." } }, { "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, and is fixed in 3.2.25.post15+tuxcare." } }, { "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, and is fixed in 3.2.25.post14+tuxcare." } }, { "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, and is fixed in 3.2.25.post14+tuxcare." } }, { "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-35192", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:11515d39-7b40-580f-9261-26b4fdc970be", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-35192 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2026-35193", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:aa5b2d31-5f08-596c-9368-5ae542c35900", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-35193 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, and is fixed in 3.2.25.post14+tuxcare." } }, { "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, and is fixed in 3.2.25.post14+tuxcare." } }, { "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, and is fixed in 3.2.25.post14+tuxcare." } }, { "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-5766", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:c20f68e8-e8b0-52f3-9f6b-a9399677708f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-5766 affects version 3.2.25.post11+tuxcare of django." } }, { "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-6907", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:59e8fbdb-1033-5235-8cf8-52e5b22dbbe8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-6907 affects version 3.2.25.post11+tuxcare of django." } }, { "id": "CVE-2026-7666", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post11+tuxcare" } ], "bom-ref": "urn:uuid:c4e59a09-eb22-5c8c-8e7f-848b57b2b71a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-7666 affects 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" } ] }