{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:fe1b5617-b8d6-582a-8fdd-a9c06001c816", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "django", "purl": "pkg:pypi/django@3.2.25.post17+tuxcare", "type": "library", "bom-ref": "pkg:pypi/django@3.2.25.post17+tuxcare", "version": "3.2.25.post17+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.post17+tuxcare" } ], "bom-ref": "urn:uuid:b9dbc7d9-32d1-545b-b1ed-74ed99ac92b7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2007-0404 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2007-0405", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:abc709c7-ceb2-5920-a56c-82bcbe4adc38", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2007-0405 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2007-5712", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:eff0274c-8d33-5b65-9350-3f6d2eb72e54", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2007-5712 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2008-2302", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:429642ea-1ef5-5a62-a52f-8b3f3f3860eb", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2008-2302 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2008-3909", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:61429c97-5269-5807-8c14-948d787d9a5d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2008-3909 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2009-2659", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:16f9496e-4e21-5877-b6ce-5f747393259c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2009-2659 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2009-3695", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:4f2b11ef-03f2-50cd-9789-3eaaf7a9fd16", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2009-3695 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2010-3082", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:2e9c1739-4944-5220-a5bd-2545223cf55e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2010-3082 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2010-4534", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:0c76c6bd-ed2c-554b-9fb2-8fe628afc3aa", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2010-4534 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2010-4535", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:b88847e0-0ac3-56c9-90cf-55452c5cddf3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2010-4535 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2011-0696", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:f9a54f0e-c15b-5785-809e-0ca37c2504da", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-0696 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2011-0697", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:16185ced-4f19-5bfa-89b5-4623f6f95ba3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-0697 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2011-0698", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:7794b85d-2da9-51f4-b8d5-0d416cbedfb3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-0698 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2011-4136", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:905d8e5d-a9ec-5f0d-ac47-8683bd034030", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4136 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2011-4137", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:e8a2a9cc-15ed-5259-88d7-6e9f2b7a2336", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4137 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2011-4138", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:13029cae-0e3a-502b-a968-fdd08a860b8d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4138 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2011-4139", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:961d3882-9b33-5b12-a499-5b9d4e309425", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4139 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2011-4140", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:64a34c05-e705-5069-9407-23bed38105d3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4140 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2012-3442", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:44714c56-0b53-53c8-8bd2-9012127a0432", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2012-3442 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2012-3443", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:3332231e-08b9-589e-b308-73e2c0b50fc7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2012-3443 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2012-3444", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:52589d0f-5ee3-5688-a0c1-db176855ba7e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2012-3444 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2012-4520", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:90e651f2-2d4e-562c-a37d-ecb39cd1134a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2012-4520 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2013-0305", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:267d9eb0-189d-522f-a8ef-930de7fa4755", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-0305 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2013-0306", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:090c8a1f-1af4-5af5-9478-a3ee6a05b8ce", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-0306 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2013-1443", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:d400f399-2411-5255-943f-94f4b500e140", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-1443 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2013-1664", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:65396ec1-b536-53e9-989e-e40cff9f4c66", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-1664 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2013-1665", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:b05a48fe-bcfc-560e-91b1-860aece12b4d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-1665 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2013-4249", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:8274bd30-7bc0-519e-84eb-2a297510305b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-4249 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2013-4315", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:bb64af8e-3a78-56cc-b5d9-dc7ac672054d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-4315 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2013-6044", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:51c09ec5-54ac-5d94-8b28-6e1e930b6ee4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-6044 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2014-0472", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:f8796f0b-171e-5ead-9691-663d97a1baf8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0472 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2014-0473", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:f9c65061-8659-566c-bbf7-dcfd950da2f0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0473 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2014-0474", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:88226fcf-0f9f-5648-a832-76de44d25aa4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0474 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2014-0480", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:f09a1fb3-3ed8-5bb7-920c-ca80fe669a50", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0480 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2014-0481", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:0a5b1e0a-7fec-5d8e-96fa-3af4ec5542d8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0481 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2014-0482", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:1d195c4f-d71b-530d-9ea0-b1cc82aa73be", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0482 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2014-0483", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:98c1bcb1-688d-5c52-8a03-2973da175d61", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0483 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2014-1418", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:5888e1c5-1efe-5562-a5ba-084f8b2e173f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-1418 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2014-3730", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:f31ed38f-42c4-5baa-80ee-5d1ea84d43fd", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-3730 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2015-0219", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:02ee0dba-ea2e-53d0-91c4-372748e0db9b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-0219 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2015-0220", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:70f13e67-839f-5874-81b5-19885015727e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-0220 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2015-0221", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:e9df8008-90ef-50f8-8390-128689449d5a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-0221 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2015-0222", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:3503cbc7-9be0-517b-a273-05ce6fc9954a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-0222 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2015-2241", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:0cc2580c-b1ea-5cfd-8aab-3942aab2f6ab", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-2241 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2015-2316", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:60c85ceb-f980-51f5-976d-a88d5af7069e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-2316 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2015-2317", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:43681100-7bce-5fca-af8a-b9ab1b646ba3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-2317 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2015-3982", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:9400b2a0-f69d-566c-a44c-af1b1d634e09", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-3982 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2015-5143", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:d0585a4d-de66-59bb-940e-d5e86f95cc71", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5143 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2015-5144", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:3d5936bc-ce21-5e36-b30b-773c3ffee99f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5144 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2015-5145", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:01ccfd77-e914-5027-96ab-9fe9254e1abe", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5145 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2015-5963", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:40981609-a5b9-585f-8262-56eee6422fad", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5963 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2015-5964", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:8d2b9429-b7b8-55f0-8703-5a2461ff779e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5964 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2015-8213", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:d50ab39f-6c04-5fd3-9f8d-c97ac9f3be8c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-8213 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2016-2048", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:7a448608-56ed-5398-996c-728c78afdbe0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-2048 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2016-2512", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:5bef4611-855f-5041-af46-edbd489c4a63", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-2512 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2016-2513", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:6c9bdd64-61e5-5814-8630-52d1c201e163", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-2513 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2016-6186", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:cfba0e17-3314-551c-9ca0-8caf3ad1b797", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-6186 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2016-7401", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:9074c137-9965-5d9a-965f-418afbea56c1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-7401 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2016-9013", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:780ef1b2-9141-51bd-85d4-1338a7a6b5a7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-9013 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2016-9014", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:91314ab6-a33d-5e25-86db-3db126bb3bbb", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-9014 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2017-12794", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:c03201dc-1ee6-526a-8bfc-52ec4c2f379e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2017-12794 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2017-7233", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:f555932e-0382-516b-9813-93de216e5978", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2017-7233 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2017-7234", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:e05d8ac4-2e32-5e86-be7b-e0cf42a19787", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2017-7234 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2018-14574", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:60dc7bf4-013c-5e2b-b1ff-c7b9f98c7577", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-14574 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2018-16984", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:3d1a851f-5a0d-5831-a69e-a92c209bdd8e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-16984 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2018-6188", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:b1b4729b-d280-519d-8b4b-a2406c6283e3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-6188 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2018-7536", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:effc92da-9cb7-538e-8ad6-302a61e4cadd", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-7536 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2018-7537", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:8bce8877-2b24-5e3b-9061-653c4d347ed7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-7537 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2019-11358", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:9f968d2a-b53e-5fd0-af78-3142b87c1bf1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-11358 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2019-12308", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:961c96ac-9939-574c-80db-b116fc32e027", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-12308 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2019-12781", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:e7b0106b-714f-5346-8ab5-24864bb56be0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-12781 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2019-14232", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:78b8c91e-d798-50d9-8a3c-e03654e52249", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-14232 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2019-14233", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:1df0b78b-3540-5c41-968e-8c4880ab69df", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-14233 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2019-14234", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:c68ceb56-a297-50aa-958b-4f24ba91ae85", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-14234 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2019-14235", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:210c0dd9-8475-5b88-a845-3a52301f4401", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-14235 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2019-19118", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:72b0505f-67c5-5cf9-bc9a-60f648fdca56", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-19118 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2019-19844", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:4497465b-4479-59b3-8f83-0765d6a75672", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-19844 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2019-3498", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:fca58d95-e944-5e48-bee9-fe3cb38e4411", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-3498 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2019-6975", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:67eeb256-7cc4-5da4-ad07-690235f8b619", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-6975 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2020-13254", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:0adfe6ca-360c-5c30-a6e3-93a5d186510f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-13254 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2020-13596", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:92c89c93-6092-5a23-9f73-0a1844f0fe36", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-13596 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2020-24583", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:729c70cc-ec3c-5fa2-9f69-9b373a65d69c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-24583 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2020-24584", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:e4b2b1db-08f9-595d-b8cc-572a74dced24", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-24584 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2020-7471", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:a388bf75-7ec7-533a-8e95-386ccc41040c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-7471 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2020-9402", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:b9f17bfa-02bd-5e23-bcd9-64856eba8368", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-9402 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2021-28658", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:f1c14979-67d3-52bb-8286-96f5e33c721d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-28658 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2021-31542", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:b0c69706-5389-5b2a-9fe3-10cd4fb32dcc", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-31542 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2021-32052", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:bc8fc227-b11a-52f9-b154-888105a67506", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-32052 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2021-3281", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:aa18a341-a2f9-555d-8201-4d6c7dffc689", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-3281 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2021-33203", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:fdf6fd6b-3163-5415-a641-d966d9fc6d8c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-33203 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2021-33571", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:cfc00e75-f47f-52fd-93b7-28c8eb9af25f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-33571 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2021-35042", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:6990974f-2c55-506e-8ef4-479314bcbc23", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-35042 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2021-44420", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:5359fc54-95fe-581d-90ea-d7f595b15460", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-44420 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2021-45115", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:92f2808e-8a0f-5ecd-b23c-f95ba022a73a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-45115 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2021-45116", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:ac4e6346-c473-5ca3-9021-2fcc47931256", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-45116 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2021-45452", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:fb13c606-c53f-5d71-b952-87d32017540c", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2021-45452 does not affect version 3.2.25.post17+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.post17+tuxcare" } ], "bom-ref": "urn:uuid:7ee5a9b4-0509-53f8-af68-6674c1e9d8ef", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2022-22818 does not affect version 3.2.25.post17+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.post17+tuxcare" } ], "bom-ref": "urn:uuid:90d9fc26-2329-5f19-a002-858ffafa6f7e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-23833 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2022-28346", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:1390208c-60e9-519d-a5f9-1b06f0b273ad", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-28346 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2022-28347", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:3aa323d8-a60d-576f-aaeb-e31f435ece49", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-28347 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2022-34265", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:616bb28f-bcde-563c-8166-a23ced26fc6f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-34265 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2022-36359", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:05cb0f68-0523-54b2-ac03-5aa44166023f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-36359 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2022-41323", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:ebe73b8f-47f8-5176-ae19-bab3d0ead3a1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-41323 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2023-23969", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:a4ff0d59-a655-525f-a6e5-5eb8c28c3877", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-23969 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2023-24580", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:292261ea-ad2c-5c1f-b41f-b91c7009e620", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-24580 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2023-31047", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:ab2dd8fc-8afd-50d5-8c6b-92b917469362", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-31047 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2023-36053", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:8b88481c-d726-5ba2-910a-323e9edacefa", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-36053 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2023-41164", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:5838cbdb-af19-5a12-ab1e-0a6a9898d866", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-41164 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2023-43665", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:bc1121bc-4ca4-55fd-9c82-def7a56e23f8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-43665 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2023-46695", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:d995ef79-5664-5ceb-b94b-b70ecc5fb056", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-46695 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2024-24680", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:337be0b0-37dd-50d2-ad56-5ed58b5aceaa", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-24680 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2024-27351", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:b749fdf8-5bc5-5b8f-8997-11ac5e547d71", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2024-27351 does not affect version 3.2.25.post17+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.post17+tuxcare" } ], "bom-ref": "urn:uuid:91bced69-951c-54f9-bf4b-7b80f97a8c20", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-38875 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2024-39329", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:97d8c8b4-13aa-53b5-9990-0777df68c0c8", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39329 is already fixed in version 3.2.25.post17+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.post17+tuxcare" } ], "bom-ref": "urn:uuid:b963d542-b0af-52d6-a830-5dbcb997e43d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39330 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2024-39614", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:d45a6858-e13e-532f-9377-fa0fe0e410da", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39614 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2024-41989", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:dbe60a73-bc7c-5ba9-b03f-9edf0f94aa23", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2024-41989 does not affect version 3.2.25.post17+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.post17+tuxcare" } ], "bom-ref": "urn:uuid:fc4246ce-4ecb-5be8-a31b-9876bc8f49e3", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-41990 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2024-41991", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:9eae2681-98ce-52d6-96ec-d4a539455a60", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-41991 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2024-42005", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:b6083243-c12b-54a1-9c6f-9cc923235df5", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2024-42005 does not affect version 3.2.25.post17+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.post17+tuxcare" } ], "bom-ref": "urn:uuid:72edfb1c-9bd0-5c0c-9c91-be4e101efc31", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-45230 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2024-45231", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:30347095-ebe0-5f39-9e19-81d8bf6c1704", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-45231 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2024-53907", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:d35d0604-39eb-5a46-ac93-6376d001b01c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-53907 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2024-53908", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:9bad6dcc-d4ca-5a93-a8da-012364fa4165", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-53908 affects version 3.2.25.post17+tuxcare of django, and is fixed in 3.2.25.post18+tuxcare." } }, { "id": "CVE-2024-56374", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:5a4ad5bd-8309-5ee6-ae51-47525dc7ef0d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-56374 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2025-13372", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:929c6e3c-f65b-5474-99af-0b3c99450df7", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13372 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2025-13473", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:33fbe523-ba00-5733-8f42-d20d35b416da", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13473 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2025-14550", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:18b0ffb1-102e-5559-a4b1-6065b42510b4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-14550 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2025-26699", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:6565e5e5-1412-56f9-949f-32f063283fc8", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-26699 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2025-27556", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:05c240fb-786f-5dee-a57b-6e985e780467", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-27556 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2025-32873", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:d0422f77-55d4-5985-8f76-6f8a37aab130", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-32873 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2025-48432", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:15980171-3f19-55cc-8335-bfa92347fc18", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-48432 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2025-57833", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:b8743b6b-a5fa-5968-a755-e73a6fe763bb", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-57833 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2025-59681", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:4cd195b1-07a1-5817-bd9f-d93fd0739941", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-59681 is already fixed in version 3.2.25.post17+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.post17+tuxcare" } ], "bom-ref": "urn:uuid:f94058de-8117-5770-93a7-65fad3918598", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-59682 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2025-64458", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:01c49713-2757-5427-a2f0-fb4e5e7a5dfe", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64458 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2025-64459", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:7e2f40c2-25e2-559f-abe1-2813a09fd664", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64459 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2025-64460", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:3c22e7d8-4bdb-57b8-a6c6-3391d9b4d667", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64460 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2026-108147", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:b2a087fb-c12c-5577-9280-4633235e8bef", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-108147 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2026-111211", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:5cdc6fd5-facf-5a8b-bbb2-509d6c5e3bbd", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-111211 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2026-111362", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:2e2cae6a-e1da-58f1-9ce0-69b080674e75", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-111362 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2026-113593", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:3fa6d56b-decf-5db2-8ac8-2888de8e7571", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-113593 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2026-113733", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:7a239af6-2715-5915-a45d-b7be056c6dbb", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-113733 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2026-114582", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:62f15775-a102-5072-af9f-83bc8ef52c63", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-114582 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2026-1207", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:91dcfa45-4c54-5d85-be5c-dfc907919501", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1207 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2026-1285", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:e66e12be-62ee-5b86-91b2-e344ef992a6d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1285 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2026-1287", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:224e636f-08e4-52fe-a5a2-34def7a781fa", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1287 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2026-1312", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:71f4b37a-b03e-5ddd-9be5-f3219c327e48", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1312 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2026-15307", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:2bb5c59a-7653-5d5f-8695-a3fb20c10a01", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15307 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2026-15830", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:1847a4cf-45e4-5cdb-a98b-35f84adaca20", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15830 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2026-25673", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:732cf5d4-4efd-57a2-9b70-b9a6dfa0275c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-25673 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2026-25674", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:36359015-3b52-5682-8f88-86b7c4f81752", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-25674 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2026-33033", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:08a4d46d-dd59-590d-8e05-1df3f3cf397f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-33033 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2026-33034", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:9d6e1853-837e-55a6-82d7-202144d61e2d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33034 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2026-35192", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:7225c78f-fdb3-5101-8053-b8629c8a404c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-35192 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2026-35193", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:ef3d699a-3c61-59a4-b086-562518b5430b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-35193 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2026-3902", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:16092666-e5de-5e3a-87d4-e055828888a2", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-3902 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2026-4277", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:2a618ea4-babc-5247-9b77-87d3fc3db152", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-4277 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2026-4292", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:b158af2c-e56f-51b4-a4d8-7fcf8df313ce", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-4292 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2026-48587", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:757c54d4-e940-5a8d-9098-07a6abb97cf4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48587 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2026-48588", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:98c30e17-14e4-53a4-8f67-2f9bf4ae388e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48588 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2026-53877", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:9f45ec98-2d1f-581a-8a06-1316d346d58d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-53877 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2026-53878", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:3632bf0f-1e07-56ec-99bb-eff71ba98260", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-53878 does not affect version 3.2.25.post17+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.post17+tuxcare" } ], "bom-ref": "urn:uuid:3c053aa9-15c2-5b1f-a9a7-e490667a917d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-5766 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2026-6873", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:04edd7e0-ebfa-56d5-ab08-63703771e6d2", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-6873 is fixed in version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2026-6907", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:c6acb349-4084-524f-a8f1-b225121bf720", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-6907 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2026-7666", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:48cccb86-96dc-547b-8856-fbe76e44d72f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-7666 affects version 3.2.25.post17+tuxcare of django." } }, { "id": "CVE-2026-8404", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ], "bom-ref": "urn:uuid:4ed832bb-f318-5cf4-9a8d-e5c3cd184f57", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-8404 is fixed in version 3.2.25.post17+tuxcare of django." } } ], "dependencies": [ { "ref": "pkg:pypi/django@3.2.25.post17+tuxcare" } ] }