{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:ec7416c0-21d6-5e7b-a07a-4c9fce2b16df", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "django", "purl": "pkg:pypi/django@3.2.25.post16+tuxcare", "type": "library", "bom-ref": "pkg:pypi/django@3.2.25.post16+tuxcare", "version": "3.2.25.post16+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.post16+tuxcare" } ], "bom-ref": "urn:uuid:e00144a0-dbda-5cab-9921-abeb623dc27a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2007-0404 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2007-0405", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:4a8eee27-6f7c-5812-afa1-a819a412ccf3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2007-0405 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2007-5712", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:3a2c8721-ef46-58ff-b006-0e117d1c4a08", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2007-5712 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2008-2302", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:aa982339-f27b-5f3c-8e35-9ce53318f931", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2008-2302 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2008-3909", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:e663ca90-bdd8-5ab3-8d2c-eb7dec58a898", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2008-3909 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2009-2659", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:f637fc0f-dbb4-5e6e-ad02-778fe9f6d2c7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2009-2659 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2009-3695", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:f8e5fb5b-4362-52e6-a61e-65d504e1b372", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2009-3695 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2010-3082", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:582c06c9-e475-51fc-bc9e-cfdfa4e7d5ff", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2010-3082 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2010-4534", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:91e626c5-d1d8-59d6-bc04-15d1f9c56df7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2010-4534 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2010-4535", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:0a701c50-c1cc-567d-bd24-bef7dc38f4ed", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2010-4535 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2011-0696", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:d6337414-f77e-5f5e-9432-f7371ff77675", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-0696 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2011-0697", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:5b038d00-b2d9-5f99-906d-1116c4e01c0e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-0697 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2011-0698", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:b9367e06-5b41-54e3-9132-2ada4562f3a8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-0698 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2011-4136", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:4608f4c0-7b48-597d-a9cc-3abf766ac8d2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4136 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2011-4137", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:b3fffe13-00f8-50bb-bd23-74d9871b654f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4137 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2011-4138", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:cccf6004-9e32-56f7-ab94-0080e58a7294", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4138 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2011-4139", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:17d0d47d-d528-5482-a07e-52bc7069bd46", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4139 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2011-4140", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:cc0b1b0e-8b46-590d-8e76-c4f9612eb539", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-4140 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2012-3442", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:2b9ec342-1796-5627-8a94-346f799804fc", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2012-3442 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2012-3443", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:ab515a48-a3cd-559c-82ca-a675093e6cac", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2012-3443 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2012-3444", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:51c9b3de-217e-5eba-989d-69b78eed226e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2012-3444 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2012-4520", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:e9ba0f8b-a7f2-57cc-b1a2-c3cbfeb21426", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2012-4520 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2013-0305", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:bb8a3bb6-3b89-5b0e-a5c1-806c036a236a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-0305 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2013-0306", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:8aae39a2-0341-5a70-afa0-1193a4b8fc28", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-0306 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2013-1443", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:ccc71ff5-1d95-5922-a635-012a2d418ab8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-1443 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2013-1664", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:522620ee-fa17-538a-9b58-d62bb661098f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-1664 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2013-1665", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:15929714-03ac-5676-84d9-fee0883fe76d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-1665 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2013-4249", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:1db2461a-08ce-5215-9dc4-da020137ff08", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-4249 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2013-4315", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:6a018de3-7c50-5f54-9943-056018779945", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-4315 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2013-6044", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:c0f22dcd-1e82-5ffa-84c5-8722906a4cad", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2013-6044 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2014-0472", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:fc4593c1-a1fc-537c-a5e3-793a085879e9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0472 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2014-0473", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:b3a3535c-ed8a-5f6f-a3bc-deb9b802e045", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0473 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2014-0474", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:8c29f26d-412d-53d0-9894-24e6d21c8da6", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0474 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2014-0480", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:9f572838-81c8-5e0c-adcc-47a72f39feb8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0480 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2014-0481", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:e4635b00-de5e-5321-8453-f078c2b3fdf6", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0481 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2014-0482", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:bbf84de7-babf-5294-b5c4-dd7d0687253e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0482 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2014-0483", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:ed26801c-919c-53b5-b3fb-ea7942eb81b0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-0483 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2014-1418", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:19d9a5c0-39cd-5de9-9466-c3dc5cc09d26", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-1418 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2014-3730", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:dce68729-70f8-5985-8e5a-5996310eafb6", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-3730 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2015-0219", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:889e4f0c-8db2-5195-9586-409b5ebc8e0d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-0219 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2015-0220", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:fcceb26c-3c21-57d9-b29f-a7e356cd1e90", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-0220 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2015-0221", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:67672d32-3577-538c-8756-10f7fae2fe04", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-0221 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2015-0222", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:5c442e27-ab81-52ef-bfda-0ffb64d10add", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-0222 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2015-2241", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:70138d3b-d9d5-51c7-b68f-c24affc01920", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-2241 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2015-2316", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:511d934c-d24f-5bb7-b640-d6e274ecb0fb", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-2316 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2015-2317", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:11914cbd-91ae-5b91-91f3-fd25ad1bb9f8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-2317 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2015-3982", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:7ca327b5-af6b-52d3-b55d-632722936607", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-3982 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2015-5143", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:a7e34fd1-7db9-51ad-a9e4-29eabf4b02e5", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5143 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2015-5144", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:b19ac86a-63dc-59a1-ab56-d27102b356ab", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5144 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2015-5145", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:61ed4ace-406f-512f-98d9-7dc2e275915a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5145 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2015-5963", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:05c3293c-815d-592c-944d-9b3514b00fcf", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5963 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2015-5964", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:36905f6a-d3d9-5b94-bdbc-b425d42a10bf", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5964 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2015-8213", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:a30ac66c-f918-5f74-bfac-d9f44e1a3da9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-8213 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2016-2048", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:ae96e80a-e6d4-5eb1-9203-7d8c2f0091d5", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-2048 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2016-2512", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:3cf5e036-aacf-51fb-a7db-d6e149aa0ce9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-2512 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2016-2513", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:10ce96cd-041d-5b88-b1b5-7fb15960da88", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-2513 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2016-6186", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:e9f6aaaa-3a75-5f0b-b0ee-1e5f93bfa55f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-6186 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2016-7401", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:4f9bd341-1832-5f3c-9ce3-d19cf82c681f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-7401 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2016-9013", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:71900029-58bf-5da4-aa55-dcb8dfc2cd49", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-9013 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2016-9014", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:788fe3e3-0bd3-56ac-a9ea-f27a82cb6368", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-9014 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2017-12794", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:188aca86-ae86-50a3-a278-dc23260705c2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2017-12794 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2017-7233", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:7a073f13-1504-5f84-a7b8-1c72866b8a6e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2017-7233 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2017-7234", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:6c30265a-9efb-55f1-a3ab-0249f0075f88", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2017-7234 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2018-14574", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:975d290c-c385-5556-aaf8-86de8f40bd27", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-14574 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2018-16984", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:43401502-52f0-5d01-8718-5c9025c7af95", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-16984 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2018-6188", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:002f2398-19e5-584c-a0d2-66019db2b631", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-6188 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2018-7536", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:c288f02b-dd51-5a05-a1ad-de40d95a9185", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-7536 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2018-7537", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:e55aee26-c694-55b2-bd7c-56749394dfa1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-7537 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2019-11358", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:3ef00d60-2f0c-55cc-a647-fccd271c80af", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-11358 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2019-12308", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:9648ed4a-fc29-59a1-8209-7a102588b466", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-12308 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2019-12781", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:e56b8d31-1070-5d8d-80aa-027d510bc2e4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-12781 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2019-14232", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:38d587a8-daf6-5592-911a-fb083c6a0201", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-14232 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2019-14233", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:560fbc1e-912c-534d-b8c1-4f8d685ff297", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-14233 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2019-14234", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:a1c36bc9-1332-5ad1-9bf4-55c853c2d7eb", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-14234 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2019-14235", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:8b007dca-e861-5022-8787-a28d529c3cc3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-14235 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2019-19118", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:4ebd38f9-84e6-555e-9df2-78ce6847904c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-19118 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2019-19844", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:dd76f3dc-49a4-5fa1-9f36-392baca1e26e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-19844 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2019-3498", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:34499f6b-916e-5d13-90e7-481f5886a3ad", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-3498 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2019-6975", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:e072c85c-7e61-5211-abdc-d2fafc584a64", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2019-6975 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2020-13254", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:e7b17c2f-3a5a-5d60-90d4-fe1315ff1a92", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-13254 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2020-13596", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:858eafa2-e213-5228-8416-224d93a2e401", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-13596 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2020-24583", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:174b9dd4-174d-5fa7-8ff2-926d1aa3eac7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-24583 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2020-24584", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:ec3716a5-50e8-5d4c-a3a7-e1bdd996fda5", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-24584 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2020-7471", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:ea1ee46a-846d-5ba1-95ba-a9d458ef48b2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-7471 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2020-9402", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:75b2342e-9e33-5466-a9e9-0d72492ee018", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2020-9402 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2021-28658", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:5067ba7f-57c6-52f4-a00d-940b180ad694", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-28658 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2021-31542", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:a150ee42-9020-5fd5-8b17-deb3115eb7c3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-31542 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2021-32052", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:e0cd7e4a-698b-528d-ab32-0c3494c23424", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-32052 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2021-3281", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:04c02ea8-8d1e-5ce0-a9bb-370e4641e36d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-3281 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2021-33203", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:1d8595f2-a4be-561d-a97e-57588cf6bbd8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-33203 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2021-33571", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:49c81e4f-67f3-5ad8-b15e-b6f1c81abe9d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-33571 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2021-35042", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:dcbfb5d3-b5aa-5021-ad75-7ab48e9c8625", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-35042 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2021-44420", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:368d044a-3cb2-5f16-9509-617f5764dbde", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-44420 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2021-45115", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:619500ef-b504-5d56-b193-932669201f5c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-45115 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2021-45116", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:8f990dcc-0d6b-5f78-b7a4-b60c9da93c72", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-45116 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2021-45452", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:89ac6acd-c44b-5ad4-bf64-049b56ff2cb9", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2021-45452 does not affect version 3.2.25.post16+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.post16+tuxcare" } ], "bom-ref": "urn:uuid:7f1afc70-168a-575e-a523-bb68743927bb", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2022-22818 does not affect version 3.2.25.post16+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.post16+tuxcare" } ], "bom-ref": "urn:uuid:ce52f5d0-ecde-579a-84d2-081057c89f40", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-23833 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2022-28346", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:75c838b5-5ab0-58bf-a294-37fd9c0d404e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-28346 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2022-28347", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:a92905f4-7a5d-526e-954b-e3a714e70055", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-28347 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2022-34265", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:02c043cb-347a-5b35-b27b-bad2c4d82525", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-34265 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2022-36359", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:18fe504f-fc65-5993-bed1-53350e065d02", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-36359 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2022-41323", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:75f6a64a-79be-57bf-937c-f22c3de485f6", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-41323 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2023-23969", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:de27f1bc-7d05-5ca4-aa36-492d59c6ffe0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-23969 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2023-24580", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:8373592a-d8ee-536c-9619-a6de1f54fe58", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-24580 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2023-31047", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:5c13141f-6bfb-51b0-a04c-7b24269afcb0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-31047 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2023-36053", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:0b6b742e-f01c-58b8-a12e-8c16445082ff", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-36053 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2023-41164", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:9df79335-1d41-5ccf-a320-f6bf3713af62", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-41164 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2023-43665", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:d5988233-79cd-560f-9d8c-5f119edebcee", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-43665 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2023-46695", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:cc674923-7d99-561e-8a23-a41dacf0bbda", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-46695 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2024-24680", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:79d9d0e0-83f9-56bf-b922-085983d2f5e7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-24680 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2024-27351", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:d4622428-5091-56f6-a867-511aa6af0ea7", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2024-27351 does not affect version 3.2.25.post16+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.post16+tuxcare" } ], "bom-ref": "urn:uuid:0b6931e0-e04d-55f9-8a0f-74f1ba31695a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-38875 affects version 3.2.25.post16+tuxcare of django, and is fixed in 3.2.25.post17+tuxcare." } }, { "id": "CVE-2024-39329", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:7177babc-4f7f-5a90-9fec-86447d997f72", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39329 is already fixed in version 3.2.25.post16+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.post16+tuxcare" } ], "bom-ref": "urn:uuid:c4780eee-63da-5f21-9d94-f7286b3953ea", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39330 is fixed in version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2024-39614", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:2600edb7-4131-595b-85b5-d6db511f5702", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-39614 is fixed in version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2024-41989", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:d6b16af9-80a2-557b-a7f0-745978a16b61", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2024-41989 does not affect version 3.2.25.post16+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.post16+tuxcare" } ], "bom-ref": "urn:uuid:d02606d5-e6ef-5b13-a34b-1c65482197af", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-41990 affects version 3.2.25.post16+tuxcare of django, and is fixed in 3.2.25.post17+tuxcare." } }, { "id": "CVE-2024-41991", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:11cd5cc5-794d-5db3-8f99-e997dd9465dc", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-41991 affects version 3.2.25.post16+tuxcare of django, and is fixed in 3.2.25.post17+tuxcare." } }, { "id": "CVE-2024-42005", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:fc2f2985-dcf0-5629-bcab-a23d21ca0939", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2024-42005 does not affect version 3.2.25.post16+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.post16+tuxcare" } ], "bom-ref": "urn:uuid:c684066a-97e1-5c39-a7e0-63e9c4948fe3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-45230 affects version 3.2.25.post16+tuxcare of django, and is fixed in 3.2.25.post17+tuxcare." } }, { "id": "CVE-2024-45231", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:269a362c-fbe7-50ff-865d-9899ebd8bfd0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-45231 is fixed in version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2024-53907", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:a396dc43-4621-5a53-9ece-b9a9b667789c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-53907 affects version 3.2.25.post16+tuxcare of django, and is fixed in 3.2.25.post17+tuxcare." } }, { "id": "CVE-2024-53908", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:0a56c670-c13c-5085-8ecc-44fb0fa6f21c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-53908 affects version 3.2.25.post16+tuxcare of django, and is fixed in 3.2.25.post18+tuxcare." } }, { "id": "CVE-2024-56374", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:f06d8d26-7d22-533d-b825-d115f18e972f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-56374 is fixed in version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2025-13372", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:b87745aa-21b7-5a7c-bde5-7068ffc678c0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13372 is fixed in version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2025-13473", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:8fc4c7b0-ef6c-5dba-9abf-c516569f309f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-13473 is fixed in version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2025-14550", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:565b311a-6e04-5e5a-ba9e-d2d160ebf585", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-14550 is fixed in version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2025-26699", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:602f483b-e40a-531c-acae-ee484342ad39", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-26699 is fixed in version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2025-27556", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:c25dde4c-21d1-5842-8080-baad8a9b7d71", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-27556 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2025-32873", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:84f2dac9-1664-5c8d-b5a7-abf88521829a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-32873 is fixed in version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2025-48432", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:17c84087-7962-576d-b258-363b7fed9cdb", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-48432 is fixed in version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2025-57833", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:dd3f8209-ea38-50a0-944c-9832d5a50835", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-57833 is fixed in version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2025-59681", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:20a13480-f413-5362-945e-9ac8a3fe9228", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-59681 is already fixed in version 3.2.25.post16+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.post16+tuxcare" } ], "bom-ref": "urn:uuid:45e58873-18c7-53f7-bc03-98f86fe0f86a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-59682 is fixed in version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2025-64458", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:43eeedf3-ae47-5e8b-8cdb-ab29573b72b7", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64458 is fixed in version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2025-64459", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:d62970b6-80be-56b0-9a92-4bddc86fe9ac", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64459 is fixed in version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2025-64460", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:5cc0d8fa-66de-570b-a05a-380a804aa103", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-64460 is fixed in version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2026-108147", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:716c1d85-f04d-5bb8-a3f1-9ee4e571ccb7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-108147 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2026-111211", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:3796cf06-fbeb-5414-badc-3c8859418355", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-111211 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2026-111362", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:b2c1e24c-b7d2-5fae-89d1-6f281fc6f025", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-111362 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2026-113593", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:e885bc04-9aed-54ee-90de-67e0ec3cd4d2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-113593 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2026-113733", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:b3d07a87-7c44-5534-b60a-4e0abf20af1f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-113733 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2026-114582", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:97a3e2e4-3342-56aa-8476-685ac72d5b48", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-114582 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2026-1207", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:fa354527-9f8a-5278-a2d7-016fbc6e9157", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1207 is fixed in version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2026-1285", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:593c498a-73ac-5258-946f-ad4ca781e396", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1285 is fixed in version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2026-1287", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:e9d62ff6-e2ed-5fa2-871f-13ff2588766c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1287 is fixed in version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2026-1312", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:3681ff92-936e-5db3-8010-5986b193d9c6", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-1312 is fixed in version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2026-15307", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:ee641746-c28d-5f2c-8e60-3e5c0c530a00", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15307 is fixed in version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2026-15830", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:a75f9ff2-4aa6-5e88-9c76-d3690aade096", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-15830 is fixed in version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2026-25673", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:ab2b751d-ad48-5304-815a-d0ab35bbbc95", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-25673 is fixed in version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2026-25674", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:ff91b4a6-01ea-5be1-a988-48294bb78c59", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-25674 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2026-33033", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:337adc2c-b86b-5fc6-bdd1-a4d87b9a52b1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-33033 is fixed in version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2026-33034", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:869af58c-64e7-581e-9a28-5a4be987e018", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33034 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2026-35192", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:e6c4cb3f-fe44-59ba-b778-7f89f5cf7f84", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-35192 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2026-35193", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:c84ce408-87a5-5ec1-9883-c8acdb37a930", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-35193 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2026-3902", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:fd563028-8a86-5bb6-a013-47e8ec2cf91f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-3902 is fixed in version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2026-4277", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:dbb510bd-7016-53cc-8898-9f2d3b2c988f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-4277 is fixed in version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2026-4292", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:043e5d0f-7833-50db-b6c2-27212f514d06", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-4292 is fixed in version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2026-48587", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:edaea4fe-fbdd-522e-8b7d-a42281b54c00", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48587 is fixed in version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2026-48588", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:12470c6f-cfdd-5b81-bb43-18f4967c4ac2", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48588 is fixed in version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2026-53877", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:182d9fd5-a944-51f9-8fac-4969c05467ce", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-53877 is fixed in version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2026-53878", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:d1962ff1-72fc-5027-94cf-2e39ceabfbd7", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-53878 does not affect version 3.2.25.post16+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.post16+tuxcare" } ], "bom-ref": "urn:uuid:767b2ad8-096b-50f2-898e-06634265ac1a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-5766 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2026-6873", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:f57fda25-f932-5128-b297-51dc429a70dc", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-6873 is fixed in version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2026-6907", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:8bbe558e-a107-5075-9283-2a57cebbdaaf", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-6907 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2026-7666", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:1fb77df2-1aca-5f09-ab6a-bc86667a070d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-7666 affects version 3.2.25.post16+tuxcare of django." } }, { "id": "CVE-2026-8404", "affects": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ], "bom-ref": "urn:uuid:c646c267-dea0-5f8a-b46d-4868ef56ec9c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-8404 is fixed in version 3.2.25.post16+tuxcare of django." } } ], "dependencies": [ { "ref": "pkg:pypi/django@3.2.25.post16+tuxcare" } ] }