{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:ca00fbd9-0939-5f83-993d-8aa5f021705a", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "django", "purl": "pkg:pypi/django@3.2.25.post18+tuxcare", "type": "library", "bom-ref": "pkg:pypi/django@3.2.25.post18+tuxcare", "version": "3.2.25.post18+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.post18+tuxcare" } ], "bom-ref": "urn:uuid:d6d4e45d-7067-5998-8d91-1fde33f6cef9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2007-0404 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2007-0405", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:5716510a-5ac8-524e-a606-aa12729dc0c0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2007-0405 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2007-5712", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:796b1b83-5ad1-544d-b6eb-debfa7d9d4b4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2007-5712 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2008-2302", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:51d24d95-3e5a-5559-ad2e-fad4aaa60b11", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2008-2302 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2008-3909", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:5962ef5d-5a0f-59a7-842a-c7ff8f6753cc", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2008-3909 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2009-2659", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:ef067558-ff58-5b18-8b94-cc6a0d01d6fd", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2009-2659 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2009-3695", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:9dbb5c59-c6d9-59c9-b09f-28df75ccdacf", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2009-3695 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2010-3082", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:9ec0a827-a559-5cb4-b08e-7cd617b9bcab", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2010-3082 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2010-4534", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:7b1c129d-8357-58df-b973-7094ed175ed1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2010-4534 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2010-4535", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:2a620f66-3ebf-58a6-8291-e7ca047bdb37", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2010-4535 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2011-0696", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:ced92a6a-6691-501f-b86f-e338e13feba4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-0696 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2011-0697", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:8d844140-b6c0-5822-9cd7-f15de64024f5", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-0697 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2011-0698", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:a8e15161-8f55-5db2-b494-bf5fec14680b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-0698 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2011-4136", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:6f2f35d3-494b-5e1a-8398-e0e3f3a76391", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4136 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2011-4137", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:7a22d351-eb3b-5427-878c-26b09910ec5d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4137 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2011-4138", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:8a73809b-9be8-5426-b21e-9663742b727f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4138 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2011-4139", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:4fb36521-889a-5c20-9afa-1adc5cefbcf2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4139 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2011-4140", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:4c1964d1-ecd6-5281-b36a-c8d31ea7766c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4140 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2012-3442", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:c0440540-32e8-5306-9f88-b2bcc394c636", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2012-3442 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2012-3443", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:08328dcd-d2f1-56ff-8969-1424bd3eddca", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2012-3443 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2012-3444", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:653f1957-431a-5a97-9731-5ae61b09573d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2012-3444 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2012-4520", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:66402b45-3e46-505b-b56d-126fa0ec4793", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2012-4520 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2013-0305", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:4817d66f-d3ca-5991-84f9-d6c21a9e4a80", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-0305 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2013-0306", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:18be4059-f38c-5e72-abb8-0651dabaf2e2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-0306 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2013-1443", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:97887cf6-2475-50f2-9f28-90bf80562aec", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-1443 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2013-1664", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:2f0d2eb0-0ff8-5240-ae43-2900955a003f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-1664 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2013-1665", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:e480f67e-3dc4-58f5-a417-3f531a089e94", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-1665 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2013-4249", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:7223704c-211c-50ce-bdff-f5d084ee2977", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-4249 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2013-4315", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:7de37ebe-8a29-55fa-a4fb-97068df5f709", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-4315 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2013-6044", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:85ff3d4c-15da-59a6-8d04-15510b82e2c0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-6044 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2014-0472", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:88e4b093-04ba-5775-a1ed-97ed41ebc1d0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0472 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2014-0473", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:cc42e950-e5e0-5381-891b-9b1cab1bea18", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0473 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2014-0474", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:7531e71b-b4ad-5e33-8433-2e90a7f743d7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0474 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2014-0480", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:a940f121-1680-5c38-bf2d-9e0be9d5824e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0480 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2014-0481", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:d33a40cb-9c00-5ed7-b0fc-31a051f70ebb", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0481 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2014-0482", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:0a5ac6ba-0f0f-514b-9874-ab832d1e31da", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0482 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2014-0483", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:29e9614c-7afe-58d8-bf54-0e8f9b775af2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0483 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2014-1418", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:6d6a6227-362e-56aa-bd2f-338d585c14bb", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-1418 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2014-3730", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:1506b57d-b67c-5df2-9907-751b981ffb3d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-3730 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2015-0219", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:5289eac0-64f5-5111-8739-5788e990193d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-0219 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2015-0220", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:378d417e-940a-5487-a5f6-c566d1b31de9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-0220 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2015-0221", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:78d3e7d8-9ca6-53eb-a087-c9f99e394e6c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-0221 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2015-0222", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:f49b6a7d-dbb0-5d8b-b57c-523d92156698", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-0222 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2015-2241", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:844a207b-68c6-54f8-b84c-5ae9309f0378", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-2241 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2015-2316", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:6725dc49-83a4-5aaf-b601-5e9d1aa7d02f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-2316 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2015-2317", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:bd044e23-26f0-595e-aff9-d30d47bcbd42", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-2317 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2015-3982", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:6ee84bdc-724f-59e4-b7a2-8c361f1bc0df", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-3982 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2015-5143", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:908d7176-804f-5c92-9838-e8315d86ff6a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5143 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2015-5144", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:64645423-bcfe-5f35-a0df-52ef0ccc2af1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5144 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2015-5145", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:5a7e82a0-96da-55a0-8244-ef1b909caa5f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5145 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2015-5963", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:41684950-4b61-596c-a2b1-944adb0f5c0d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5963 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2015-5964", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:decb7061-0415-51a8-8a56-54ca3500ff2e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5964 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2015-8213", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:ef81b648-7336-5986-8a3e-478affa91ce7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-8213 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2016-2048", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:27056750-b7e6-5195-ab9c-b293aedbed1c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-2048 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2016-2512", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:96ba99a8-54f5-5578-96c2-6fbb83b43974", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-2512 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2016-2513", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:e6e1db7b-35f3-52a4-abac-0ad9e869c281", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-2513 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2016-6186", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:3e1b9c26-65e4-5a74-a738-0cc6ebc8c8d3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-6186 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2016-7401", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:a24ddd13-0664-501b-bd75-66be24075f22", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-7401 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2016-9013", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:2f073b22-094c-57b7-8e28-14d4222be3e6", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-9013 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2016-9014", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:38281974-367b-51d4-bf3c-44c9aeb802b6", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-9014 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2017-12794", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:0975e68f-8ba3-5b8c-955e-6a750b7052c6", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2017-12794 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2017-7233", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:783f4767-8b2f-52fd-b7be-a5247915278d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2017-7233 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2017-7234", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:d08beced-c241-5274-9773-9a936cc5dd99", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2017-7234 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2018-14574", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:4e914c69-1603-502d-902e-2cbaea27d0e1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-14574 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2018-16984", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:7ae92e66-6a72-5696-8ccd-be245c5811a7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-16984 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2018-6188", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:d2de9f60-e16d-5aaf-acad-3e39e323e1bb", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-6188 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2018-7536", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:4f9f8cc2-327b-5548-836d-d8904b914b52", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-7536 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2018-7537", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:1e3f25c0-d940-5f2f-9035-93abc60a5f5a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-7537 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2019-11358", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:1f6fc49d-1467-5ef5-925e-b2d2d7e86855", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-11358 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2019-12308", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:1bb501e5-79cb-5a8c-91ab-611d7236d7b6", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-12308 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2019-12781", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:f63122a1-8b6a-5522-8bc8-561456560e71", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-12781 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2019-14232", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:788415e7-abdb-55ee-a2e9-937e315e40dc", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-14232 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2019-14233", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:b805d673-271f-5013-ba24-bf0d9650d196", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-14233 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2019-14234", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:faf10f6a-8957-5950-8711-7432a0f0b77a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-14234 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2019-14235", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:ddbecac8-ffed-508c-b4ca-d07e98ae1c27", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-14235 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2019-19118", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:1d8e5013-96b7-51a8-bb85-0f7377cc3fea", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-19118 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2019-19844", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:e0736c5c-8aa6-5b99-a453-87bd7978c4e2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-19844 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2019-3498", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:301c9d33-2029-5c81-b0cd-359d297b3609", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-3498 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2019-6975", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:f153f495-cb74-5224-9bb3-19162bdfd0aa", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-6975 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2020-13254", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:66e5fa8b-2920-5bbb-853d-511f09675523", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-13254 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2020-13596", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:1e78b723-4507-5e80-a7f6-4d19a38d465d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-13596 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2020-24583", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:c1299ec8-1acd-5f9b-8d55-b52e074467f8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-24583 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2020-24584", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:35668fa7-3c24-5c0e-aa61-0e66662003e6", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-24584 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2020-7471", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:f6ed54b7-132e-5214-a1a9-7577e0d23d7e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-7471 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2020-9402", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:692b7a50-09fb-5b0d-b0ed-4559f01c3a3b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-9402 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2021-28658", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:04945350-af6e-57e0-8b18-16580e55cef8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-28658 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2021-31542", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:fb6cfb83-0d72-521c-9baf-1dca09f40abd", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-31542 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2021-32052", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:446de70a-5b1c-5f7c-b11e-1f6e1171c1b9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-32052 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2021-3281", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:f88c5883-a585-5fab-b5ad-ebea835bbc32", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-3281 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2021-33203", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:1bf37e80-a99b-5364-843d-29fa3bd98a18", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-33203 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2021-33571", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:95ca568a-42d7-5cdc-b60f-b8091fc3dcc7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-33571 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2021-35042", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:c7cf4534-7f3f-521e-bf65-046490c21f5e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-35042 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2021-44420", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:098f5b26-73c4-5a62-b636-c244daf7c7fc", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-44420 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2021-45115", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:9936c4b3-0497-57cd-b92a-215fdfb475ce", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-45115 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2021-45116", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:6e9ab099-f2b2-59ed-9591-9cd045736b00", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-45116 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2021-45452", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:7aff2a89-4b0e-52ba-a844-7fa3933a5a49", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2021-45452 does not affect version 3.2.25.post18+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.post18+tuxcare" } ], "bom-ref": "urn:uuid:29a0c44b-7a12-563c-a1d7-292ec198a15d", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2022-22818 does not affect version 3.2.25.post18+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.post18+tuxcare" } ], "bom-ref": "urn:uuid:33c4696a-8742-5b25-8c53-2d876f7ae2ea", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-23833 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2022-28346", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:65a91f09-fb49-52f7-8f7f-20a39a01e264", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-28346 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2022-28347", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:1722d67e-2ad7-5487-a710-f96f39c75f97", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-28347 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2022-34265", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:24bf2b20-df4a-57d4-ae4a-39b1545b1098", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-34265 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2022-36359", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:c78041e7-3584-5691-ac49-726bf403bbb1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-36359 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2022-41323", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:2662506c-eddd-54c4-b2c4-131430c47e55", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-41323 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2023-23969", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:a0d074b1-7f81-5bfa-aab7-a54a88ffa8f4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-23969 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2023-24580", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:5fa64f50-981c-5baf-99b1-e5723e9f6060", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-24580 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2023-31047", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:d609d353-d948-5cf9-b30c-007da29c2786", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-31047 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2023-36053", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:db466c93-8e2f-5686-b408-3300d7030a59", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-36053 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2023-41164", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:fa2eafbc-37a1-5a4f-85d9-85d1c5d67844", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-41164 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2023-43665", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:559e8998-3812-59ce-b2a5-2692eb65714d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-43665 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2023-46695", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:c3f30af0-d4cb-5a54-ae24-cd160de5fae1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-46695 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2024-24680", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:f362d14c-ed7f-59dc-b485-63ffd2fb925e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-24680 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2024-27351", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:1b1c8bf8-3f66-59a4-b057-01e9cba9a8f0", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2024-27351 does not affect version 3.2.25.post18+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.post18+tuxcare" } ], "bom-ref": "urn:uuid:96408ad9-65e6-53ab-b52b-c0f8a322b76a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-38875 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2024-39329", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:13e4ce89-3220-5312-91fd-cff41d62b5dc", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39329 is already fixed in version 3.2.25.post18+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.post18+tuxcare" } ], "bom-ref": "urn:uuid:b7c3cf00-1bee-5072-a036-e706d0a68d1a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39330 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2024-39614", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:7e17b5e5-68f7-57f4-bdb8-291bc717b876", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39614 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2024-41989", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:b53e5c0b-3f2c-5939-8e72-8f749624a948", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2024-41989 does not affect version 3.2.25.post18+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.post18+tuxcare" } ], "bom-ref": "urn:uuid:97b7f6c5-e8fe-5efb-8228-31fa3bb4a456", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-41990 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2024-41991", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:176cbeb8-914e-5f6c-8529-8b32bacecfdb", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-41991 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2024-42005", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:5babfcdd-7231-5c83-ac73-9af54ffccd2b", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2024-42005 does not affect version 3.2.25.post18+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.post18+tuxcare" } ], "bom-ref": "urn:uuid:22b15637-6ebb-54c2-b6df-19f175e4dd4f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-45230 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2024-45231", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:e019032e-bfbf-56b8-a07a-cb785336ce0e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-45231 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2024-53907", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:354ccf9e-28ca-52a3-a6f6-aeb2b7f1e1fa", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-53907 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2024-53908", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:ed9c3a99-9f16-57bd-a9d0-ab5003428561", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-53908 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2024-56374", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:20496c76-b011-5808-91fc-9474115b03aa", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-56374 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2025-13372", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:fcc42233-8b23-53c0-ad11-e35bd5651cb3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13372 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2025-13473", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:19deffc6-5714-55e1-8867-1a5196ef8f9e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13473 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2025-14550", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:e3368755-a4c5-5fb1-8c44-ae1097c797ea", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-14550 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2025-26699", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:ef4c7622-94c9-55b5-9ee8-1efee096d14d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-26699 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2025-27556", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:3997f053-6cd4-5897-ac67-5c038cb76adc", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-27556 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2025-32873", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:ce37c89e-9fe6-5e73-ab7d-b5c908e6c427", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-32873 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2025-48432", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:9e7a2393-47b2-5117-bb8c-953e314b638a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-48432 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2025-57833", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:7e31d4a2-9623-5492-a97a-7c98cebde98a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-57833 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2025-59681", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:180bc618-0890-5494-9104-debd167ca8a1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-59681 is already fixed in version 3.2.25.post18+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.post18+tuxcare" } ], "bom-ref": "urn:uuid:ffa7890f-1245-56dc-a982-3227dda96639", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-59682 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2025-64458", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:99fbd285-c86b-57d2-a50c-8e6604a75417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64458 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2025-64459", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:0f02f355-996c-5be7-8704-590847ca424f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64459 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2025-64460", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:6c85a051-965a-50de-a158-3b7cb1e55e21", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64460 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2026-108147", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:e976ea72-bc5e-52e2-b6a5-164aa22e6a53", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-108147 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2026-111211", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:fd50b5d4-31cf-5134-9b61-e1ccc6ecacb3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-111211 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2026-111362", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:d916e438-8377-5347-98f7-9041900ce9e4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-111362 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2026-113593", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:138ecad3-42d3-5776-8618-fcc6c9eda3f1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-113593 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2026-113733", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:9a324193-719b-56ea-abae-232ce28e7c02", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-113733 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2026-114582", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:31d99c14-edda-59b1-bf1a-119d54017ba7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-114582 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2026-1207", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:d543475b-d674-5b43-b41e-1ab2a0f7d90f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1207 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2026-1285", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:6fd2c685-a9fc-5528-b9d9-54cdf6bd2b0a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1285 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2026-1287", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:ac0f71ac-96bd-5582-935e-95a924f2580f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1287 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2026-1312", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:a6fd076d-c589-551e-b096-4bd49028008b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1312 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2026-15307", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:b2524501-fda4-54c1-942c-fa8ba38435ca", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15307 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2026-15830", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:8eff2f25-8c3b-56f0-b2ab-956b217459b9", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15830 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2026-25673", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:ac8bd687-e787-5c6e-ae2e-6e820aba1b55", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-25673 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2026-25674", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:7f85859b-9181-54e9-8234-c2f78cb1b8a4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-25674 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2026-33033", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:eecad737-1b3e-5d0d-9dfd-cfca23e21fdc", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-33033 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2026-33034", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:1125a76d-26d9-5c34-882c-8fb7cc92595d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33034 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2026-35192", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:0bb3aadd-29a8-597d-b42d-ad77511400d7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-35192 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2026-35193", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:353bb1b7-404e-5d68-918f-185de04b8b6b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-35193 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2026-3902", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:c9cf89ed-1370-5883-a523-ced2fdc61cfd", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-3902 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2026-4277", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:95a82e56-61cb-5816-b0c9-ef412472e142", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-4277 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2026-4292", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:a8a4b375-f49c-5c04-8df2-a9633a4281ad", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-4292 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2026-48587", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:22ba1da7-c785-5d6d-8ef8-ff984b95ab6b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48587 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2026-48588", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:61b32de8-b7db-5995-ac19-18125d139858", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48588 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2026-53877", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:069cfbf0-19ab-5cfa-a24e-5c3cacb1c7ff", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-53877 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2026-53878", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:b93567d1-5ff9-5898-9c03-d77d939bf10e", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-53878 does not affect version 3.2.25.post18+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.post18+tuxcare" } ], "bom-ref": "urn:uuid:9273a872-6e4b-5121-ab7f-5a89bc5da7ba", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-5766 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2026-6873", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:dbf993f2-6204-547f-bb71-8f4080300a5c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-6873 is fixed in version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2026-6907", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:0c6b1b90-062d-59e1-a8e8-171b5abadf54", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-6907 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2026-7666", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:e0055522-191c-59ee-930d-f8e93c9c5644", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-7666 affects version 3.2.25.post18+tuxcare of django." } }, { "id": "CVE-2026-8404", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ], "bom-ref": "urn:uuid:d2e79818-d79d-54b4-aa83-15bba5ce8dd0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-8404 is fixed in version 3.2.25.post18+tuxcare of django." } } ], "dependencies": [ { "ref": "pkg:pypi/django@3.2.25.post18+tuxcare" } ] }