{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:1066bd3e-c449-5f86-a2d8-1cbf60351066", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "django", "purl": "pkg:pypi/django@3.2.25.post14+tuxcare", "type": "library", "bom-ref": "pkg:pypi/django@3.2.25.post14+tuxcare", "version": "3.2.25.post14+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.post14+tuxcare" } ], "bom-ref": "urn:uuid:12290553-0459-5ce8-9e4b-f6222675a44d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2007-0404 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2007-0405", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:e7cc0122-75c5-5f2e-a107-076d4c56fa18", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2007-0405 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2007-5712", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:c03eee46-7e4a-54e1-a5fc-ffdb17650e0f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2007-5712 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2008-2302", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:d4f4c853-e319-530e-993e-9e282f0c9d25", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2008-2302 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2008-3909", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:ccd99380-7b44-55b1-9d85-724e9ff77691", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2008-3909 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2009-2659", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:91caa8e5-a822-563b-abff-b7406f48f5cb", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2009-2659 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2009-3695", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:b7440094-6b21-5e5d-8471-e6e17449ac2a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2009-3695 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2010-3082", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:f844f92d-3433-5fa7-828b-c343f47ee197", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2010-3082 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2010-4534", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:96beed4c-0d81-506b-a21a-294b9332b6fc", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2010-4534 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2010-4535", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:d6f4ec43-0b22-53ed-8e38-90ebfe81d71d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2010-4535 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2011-0696", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:5df9f5e8-647a-5e8e-8066-485130d951d0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-0696 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2011-0697", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:9faa2fab-7f87-52aa-a3a7-750de9fc761c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-0697 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2011-0698", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:0fa4b770-5315-5cfc-821b-d8a9c590c45c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-0698 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2011-4136", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:77815c81-07d8-5508-acd2-e0774445532b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4136 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2011-4137", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:cce01274-b20f-5e96-a8b9-a0a8aec65a18", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4137 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2011-4138", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:97a8510a-3bb5-579a-99de-4c73bd23f303", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4138 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2011-4139", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:1c739305-6ba8-56d6-b867-e946f0541f60", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4139 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2011-4140", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:5c387f19-c2b2-5fe9-8904-356530581375", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4140 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2012-3442", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:03382134-be50-5e38-b25b-269ef30c926e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2012-3442 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2012-3443", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:d5385ea0-c703-5e58-a7d8-95e029fc59be", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2012-3443 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2012-3444", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:6fe21622-3c10-5cd9-965b-4c1ae5e8185a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2012-3444 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2012-4520", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:e7c10f31-446a-5a00-8331-c85f8a9da9be", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2012-4520 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2013-0305", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:ebedb4ca-05b9-535a-8d1a-b5eed3ef7bf5", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-0305 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2013-0306", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:4c3938b7-3dc7-5ad1-97da-4591b1af9ae6", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-0306 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2013-1443", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:e94d0a97-431e-5ba9-a7ef-bc886702d284", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-1443 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2013-1664", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:19137b4b-7659-50fa-83f5-6272ef1f9577", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-1664 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2013-1665", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:f86c5f09-ddce-5643-af3e-e88f925e7688", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-1665 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2013-4249", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:6b2c72c0-c159-5f11-9af9-670d645f851f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-4249 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2013-4315", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:fbeef1b3-d2ae-5f52-913a-19b7b49fde51", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-4315 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2013-6044", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:80b31588-ada2-592b-a814-547764bdd12a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-6044 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2014-0472", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:25f43ce9-5b6c-56a1-9e7c-a8c707f76c30", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0472 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2014-0473", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:195baa5c-c8c2-5781-aea5-ac445df9d6f1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0473 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2014-0474", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:2d81add6-9458-5caa-9549-934e3dd3bb46", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0474 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2014-0480", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:e4d0eb03-7c6b-5d02-a340-7cb285109f7a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0480 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2014-0481", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:88801cc8-2661-579f-a888-befc8723468c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0481 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2014-0482", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:27c2e1dc-a07b-5594-bccb-655208047d0f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0482 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2014-0483", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:0a25ec2f-5598-566c-9329-31ec5b699227", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0483 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2014-1418", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:5a5b8801-28b0-5b7d-abf9-4da1f6196640", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-1418 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2014-3730", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:5fb0c3b6-8756-56f5-a3a9-9edac7fa8bc6", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-3730 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2015-0219", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:256074d6-92d1-5257-ab93-1ee58631179e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-0219 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2015-0220", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:a42f4d87-5bb8-585b-a2ed-ecfb53f06359", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-0220 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2015-0221", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:c51437fa-7cd2-5622-995f-d929dbf75c29", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-0221 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2015-0222", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:5863d1a3-67aa-571c-ae73-29a32b6805c0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-0222 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2015-2241", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:a4024b01-eb74-5484-9d48-57710d9f9020", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-2241 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2015-2316", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:00874f7a-7fc6-5541-a54b-c632f5b63ae6", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-2316 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2015-2317", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:b7648a81-c7f9-5c2c-8ece-be37a51021fe", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-2317 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2015-3982", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:4e5acd03-7228-5b1f-9d01-7e1182308940", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-3982 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2015-5143", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:42614d4d-7566-5cd9-bd9e-dc37a0ca379c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5143 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2015-5144", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:3234dd14-9765-5917-8f38-c15834ed2ab2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5144 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2015-5145", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:8e20c6f7-9987-50a6-8c21-4f6721167017", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5145 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2015-5963", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:7b6a9089-1574-5bd1-8666-cadfd4eecdd2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5963 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2015-5964", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:096b6f0f-ce94-5d09-93a5-6c7e23d84084", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5964 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2015-8213", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:4a41ec58-f500-51c2-9029-3344344e6392", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-8213 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2016-2048", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:31611bb6-0123-5fba-95af-6480e085a9ae", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-2048 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2016-2512", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:7f4a0bf6-c2aa-523e-ba9c-074885d9b093", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-2512 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2016-2513", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:ecc5d2fa-e88a-59b3-b08d-2485acb07743", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-2513 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2016-6186", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:f28a0cb0-4085-597a-b7b2-816a334e83fc", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-6186 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2016-7401", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:83b97527-6c56-513d-8844-fd27329d0c47", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-7401 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2016-9013", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:bdfa607b-b607-5b63-9cd8-9bcefc664408", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-9013 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2016-9014", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:04f94d8b-b5f5-588c-a69f-4f3ce1c882ed", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-9014 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2017-12794", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:577ddb48-5127-5c65-ba70-c6baea891868", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2017-12794 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2017-7233", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:a2506d69-e9a0-58ac-befe-9d8a96830cca", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2017-7233 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2017-7234", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:93f09713-c2f2-588e-b95b-1778c4af803d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2017-7234 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2018-14574", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:dfd31193-22c0-5c17-b557-97f46b468b6f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-14574 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2018-16984", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:8882d674-f584-5718-96cf-b31f2793bb85", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-16984 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2018-6188", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:81371ac5-3223-5557-b55f-e28a67424507", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-6188 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2018-7536", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:5849c191-b15b-5332-b8f8-9cdca3eb0c1d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-7536 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2018-7537", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:b08177ac-04ad-5898-8841-50491ea47efa", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-7537 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2019-11358", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:335fecb1-3674-5704-adc3-0712c3d54158", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-11358 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2019-12308", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:5020c33c-a7d0-5a27-a8e9-6d62532bd739", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-12308 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2019-12781", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:59e1587f-319a-528c-baf2-dd708d0bb60f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-12781 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2019-14232", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:535c5509-d7c3-59ca-85cb-b8e8631b9627", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-14232 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2019-14233", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:f063a069-f526-5620-a0b2-c7044cf93817", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-14233 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2019-14234", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:37dab998-b4d4-5268-9a21-d35c1484c141", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-14234 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2019-14235", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:38c40ec9-cc61-5823-b655-412687839a87", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-14235 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2019-19118", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:37b0d7e5-5971-530c-943e-55cbcc70ad58", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-19118 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2019-19844", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:909cdbde-7a34-5728-944a-9f64e6c1d73b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-19844 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2019-3498", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:9e3fb8d7-fc68-586c-8976-5495854f7204", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-3498 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2019-6975", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:330aad87-e84d-5022-a720-8f770a1817cf", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-6975 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2020-13254", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:508792f8-0d3d-5bc0-9f80-a90b8d39d23b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-13254 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2020-13596", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:4db37b99-60d5-5e39-bc4c-8fcbe6c827f0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-13596 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2020-24583", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:8712a527-c183-53d0-a99d-b36a3d0f1da7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-24583 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2020-24584", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:48442da7-9edc-511d-b3e7-8e3e276e0715", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-24584 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2020-7471", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:0fd95b25-9a4d-5b42-8f06-ba36d547b581", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-7471 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2020-9402", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:db96592f-ad58-542f-a175-5133d3481689", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-9402 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2021-28658", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:10fad207-4b9a-52f9-a276-84d3db4e363c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-28658 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2021-31542", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:026c0952-d070-50ec-aa8f-f5477697dc61", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-31542 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2021-32052", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:f54efb0d-6432-5d08-87e5-3c59dfe7c8ce", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-32052 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2021-3281", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:e2484b5f-0999-558b-9098-33ce1fb1ee54", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-3281 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2021-33203", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:3ee9f121-3444-5c39-ab8a-1ca27aff39ff", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-33203 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2021-33571", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:a3e5ec0b-b06b-53fd-941c-b0c1e01ddfc2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-33571 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2021-35042", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:26956482-73b7-51fd-a391-a0d269f5578d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-35042 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2021-44420", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:954b93e4-3c3b-5dd0-9d8c-37c48d846a9d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-44420 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2021-45115", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:1e2bace3-77a9-5b9e-a3b3-ef44cf17a954", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-45115 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2021-45116", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:78c7b2dc-d34c-5d1f-995d-142c9bf527fc", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-45116 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2021-45452", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:ce353fdf-ad07-52a1-8ee1-4e6750200c5e", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2021-45452 does not affect version 3.2.25.post14+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.post14+tuxcare" } ], "bom-ref": "urn:uuid:b376dc6e-870e-5769-912f-73f09410c7ee", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2022-22818 does not affect version 3.2.25.post14+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.post14+tuxcare" } ], "bom-ref": "urn:uuid:aa8ef4de-8e09-5917-be9c-e6394510fdb9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-23833 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2022-28346", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:0a823e62-acd8-51f1-ad4f-21096ea2dd24", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-28346 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2022-28347", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:362aa563-39e0-5c6e-adca-04f258dc7e93", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-28347 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2022-34265", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:41ad004c-8b9a-5ae5-87a0-71bff0e9c3f0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-34265 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2022-36359", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:f2903290-9749-5b48-abf5-f70a94ace34e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-36359 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2022-41323", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:b0fc2b4d-6a7b-503f-89eb-6bef6789ee1a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-41323 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2023-23969", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:0d1a5869-6607-53c1-8d3b-ba7b893b9728", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-23969 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2023-24580", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:a321a647-907d-5358-a263-0b5a0527517c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-24580 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2023-31047", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:381983d0-4c89-5110-866c-c074a5b22c87", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-31047 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2023-36053", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:392c6c96-42b7-54df-b726-3d06170ced79", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-36053 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2023-41164", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:54e9ea5b-2998-501a-aed7-f2d435f1810c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-41164 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2023-43665", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:78a67deb-1743-560f-9d71-41229145be49", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-43665 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2023-46695", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:a6b4a6a4-bafe-5c85-84d3-ff03b4844312", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-46695 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2024-24680", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:0e624214-35c7-5687-adf6-69cdce0f9797", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-24680 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2024-27351", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:55c8c795-6af6-5eb2-831a-19580b75ca93", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2024-27351 does not affect version 3.2.25.post14+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.post14+tuxcare" } ], "bom-ref": "urn:uuid:ba9d1091-9bc8-5e98-becc-11c5f8364b6e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-38875 affects version 3.2.25.post14+tuxcare of django, and is fixed in 3.2.25.post17+tuxcare." } }, { "id": "CVE-2024-39329", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:6b1a402f-da75-5d9f-b0ac-d0f7d6ba1b1e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39329 is already fixed in version 3.2.25.post14+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.post14+tuxcare" } ], "bom-ref": "urn:uuid:12bd53d2-083d-5d55-9a33-7e91a63a7103", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-39330 affects version 3.2.25.post14+tuxcare of django, and is fixed in 3.2.25.post16+tuxcare." } }, { "id": "CVE-2024-39614", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:30dd0378-a0a6-5214-b450-4abb3f4b725d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-39614 affects version 3.2.25.post14+tuxcare of django, and is fixed in 3.2.25.post16+tuxcare." } }, { "id": "CVE-2024-41989", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:4ee0ade1-1a43-53c0-afd5-fc0f93546033", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2024-41989 does not affect version 3.2.25.post14+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.post14+tuxcare" } ], "bom-ref": "urn:uuid:921637e9-0cfc-5fb1-bf3b-7511f8f77c06", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-41990 affects version 3.2.25.post14+tuxcare of django, and is fixed in 3.2.25.post17+tuxcare." } }, { "id": "CVE-2024-41991", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:a1b92774-957d-561f-a870-22b217ad9cc8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-41991 affects version 3.2.25.post14+tuxcare of django, and is fixed in 3.2.25.post17+tuxcare." } }, { "id": "CVE-2024-42005", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:3472e7e6-beda-5ffd-9318-02ecf9eca284", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2024-42005 does not affect version 3.2.25.post14+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.post14+tuxcare" } ], "bom-ref": "urn:uuid:ce54533d-3c8d-5f52-a541-6fac802113de", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-45230 affects version 3.2.25.post14+tuxcare of django, and is fixed in 3.2.25.post17+tuxcare." } }, { "id": "CVE-2024-45231", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:b4119179-215f-55eb-8d5f-fe9af642cbb3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-45231 is fixed in version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2024-53907", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:5b06d701-5b0e-5a4e-9f86-165b47dada73", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-53907 affects version 3.2.25.post14+tuxcare of django, and is fixed in 3.2.25.post17+tuxcare." } }, { "id": "CVE-2024-53908", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:f840d7bb-f247-560e-90f9-77be86c9d4fe", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-53908 affects version 3.2.25.post14+tuxcare of django, and is fixed in 3.2.25.post18+tuxcare." } }, { "id": "CVE-2024-56374", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:e53f96d0-c3e7-5980-92dc-6e706a601735", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-56374 affects version 3.2.25.post14+tuxcare of django, and is fixed in 3.2.25.post16+tuxcare." } }, { "id": "CVE-2025-13372", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:008e06cb-d085-5cfb-b933-a6c2b2c3e352", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13372 is fixed in version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2025-13473", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:a94e4305-e2ef-54a8-a491-1ed772548ec4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13473 is fixed in version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2025-14550", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:1c0ef7a7-94c0-527f-b123-cc2980c67649", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-14550 is fixed in version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2025-26699", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:503b9a86-e8df-5b94-85e7-c05ba70410f7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-26699 affects version 3.2.25.post14+tuxcare of django, and is fixed in 3.2.25.post16+tuxcare." } }, { "id": "CVE-2025-27556", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:9ebfddde-c35d-5159-80b0-4a4c9e8c4fec", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-27556 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2025-32873", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:d1ba0ea2-5708-55e7-8f0a-42cc282f98c2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-32873 affects version 3.2.25.post14+tuxcare of django, and is fixed in 3.2.25.post16+tuxcare." } }, { "id": "CVE-2025-48432", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:c967c35d-a087-5ded-936f-3883207de614", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-48432 is fixed in version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2025-57833", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:f02fd849-a314-5251-ae6e-bcff25da6733", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-57833 is fixed in version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2025-59681", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:3929f10b-26c2-5bbb-899f-f264ea692962", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-59681 is already fixed in version 3.2.25.post14+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.post14+tuxcare" } ], "bom-ref": "urn:uuid:08636305-712c-57d8-a230-24c42c8bfeaa", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-59682 affects version 3.2.25.post14+tuxcare of django, and is fixed in 3.2.25.post16+tuxcare." } }, { "id": "CVE-2025-64458", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:4b8a9305-68f0-5e13-878d-ebad651d4a29", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64458 is fixed in version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2025-64459", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:0c322459-86b0-5b2e-bdfb-7fc155db7ca2", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64459 is fixed in version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2025-64460", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:3cc2c576-594f-5ba0-aa5b-f64e4084f1eb", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64460 is fixed in version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2026-108147", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:db79793a-984a-545e-9e3e-a7d6be9d9c33", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-108147 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2026-111211", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:7852f833-7da4-5faf-b8b8-5d31265823d1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-111211 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2026-111362", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:a811fd7f-b945-5c5a-868f-13f47a661353", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-111362 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2026-113593", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:a192f122-1047-5ee9-aa39-03d2ef13a460", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-113593 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2026-113733", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:468884a9-ab20-504c-aecd-0d323351bf26", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-113733 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2026-114582", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:ecb30b1b-f0b6-577c-af70-b8ffd571490a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-114582 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2026-1207", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:df081312-b029-5dce-9b7e-695cf7769ec7", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1207 is fixed in version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2026-1285", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:41da42f2-4ecb-5792-888b-4edf5aa8f76a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1285 is fixed in version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2026-1287", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:a77f4bc8-ccd3-5fbb-bd74-570d45db6297", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1287 is fixed in version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2026-1312", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:f17b66b1-8e8d-5583-97bf-90f4bd16f026", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-1312 affects version 3.2.25.post14+tuxcare of django, and is fixed in 3.2.25.post15+tuxcare." } }, { "id": "CVE-2026-15307", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:39b611f0-4c1b-5665-98a8-63639c63136a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15307 is fixed in version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2026-15830", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:5617e51a-1b8b-565e-b0ab-d8ad862caf0d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15830 is fixed in version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2026-25673", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:a7163a39-8267-5a0d-87b9-d5bbb377c92c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-25673 is fixed in version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2026-25674", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:069c0ebd-d825-5c73-95c5-3c9e2b8c6479", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-25674 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2026-33033", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:e5e5a78e-e38d-50b0-9b10-42c1c4797044", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-33033 is fixed in version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2026-33034", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:9e2edf82-c8a5-5535-ab93-800779133694", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33034 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2026-35192", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:27119cda-b1df-5c4c-843b-64fe1347b4a1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-35192 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2026-35193", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:d38a5cc0-527c-5fa3-91c3-875d4928b724", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-35193 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2026-3902", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:5ac27dc9-fd62-5a4e-bc71-19a4f30f8d95", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-3902 is fixed in version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2026-4277", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:e64ed3ba-9acd-5efd-be5b-55a130052a8b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-4277 is fixed in version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2026-4292", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:8a29e173-2205-5324-87ec-74d3cfc9c29a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-4292 is fixed in version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2026-48587", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:50980c90-7092-55ae-80aa-9a103c0c2142", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48587 is fixed in version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2026-48588", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:2437c935-37ed-5dfa-b960-7dbf6a882448", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48588 is fixed in version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2026-53877", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:e4c83166-e80a-5c0a-b3c4-8dc14694c1d5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-53877 is fixed in version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2026-53878", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:f0b35d68-33c0-52cd-8674-13de057ffeaa", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-53878 does not affect version 3.2.25.post14+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.post14+tuxcare" } ], "bom-ref": "urn:uuid:b809c566-0426-5f65-ab66-2f23e1431a13", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-5766 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2026-6873", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:d2874490-7691-5f14-b737-a4b55d89e8d0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-6873 is fixed in version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2026-6907", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:06ca0b32-c1df-584d-9ac9-1ab62564b49d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-6907 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2026-7666", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:8df0b887-0c70-5268-992e-8314fd900881", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-7666 affects version 3.2.25.post14+tuxcare of django." } }, { "id": "CVE-2026-8404", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ], "bom-ref": "urn:uuid:55399dc3-99bd-5d9d-b84c-1e2cfdca1bde", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-8404 is fixed in version 3.2.25.post14+tuxcare of django." } } ], "dependencies": [ { "ref": "pkg:pypi/django@3.2.25.post14+tuxcare" } ] }