Closed ambv closed 3 months ago
Before we go to Django 3.2 and 4.x after that, the simplest way to get rid of a few CVEs is to upgrade to the last version of 2.2.x. That puts us on par with 3.2.13 and 4.0.4 security-wise.
Before we go to Django 3.2 and 4.x after that, the simplest way to get rid of a few CVEs is to upgrade to the last version of 2.2.x. That puts us on par with 3.2.13 and 4.0.4 security-wise.