Django security releases issued: 3.2.10, 3.1.14, and 2.2.25
In accordance with our security release policy, the Django team is issuing Django 3.2.10, Django 3.1.14, and Django 2.2.25. These release addresses the security issue detailed below. We encourage all users of Django to upgrade as soon as possible.
CVE-2021-44420: Potential bypass of an upstream access control based on URL paths
HTTP requests for URLs with trailing newlines could bypass an upstream access control based on URL paths.
This issue has low severity, according to the Django security policy.
Thanks to Sjoerd Job Postmus and TengMA(@te3t123) for the report.
Affected supported versions
- Django main branch
- Django 4.0 (which will be released in a separate blog post later today)
- Django 3.2
- Django 3.1
- Django 2.2
Patches to resolve the issue have been applied to Django's main branch and the 4.0, 3.2, 3.1, and 2.2 release branches. The patches may be obtained from the following changesets:
- On the main branch
- On the 4.0 release branch
- On the 3.2 release branch
- On the 3.1 release branch
- On the 2.2 release branch
The following releases have been issued:
- Django 3.2.10 (download Django 3.2.10 | 3.2.10 checksums)
- Django 3.1.14 (download Django 3.1.14 | 3.1.14 checksums)
- Django 2.2.25 (download Django 2.2.25 | 2.2.25 checksums)
The PGP key ID used for this release is Mariusz Felisiak: 2EF56372BA48CD1B.
General notes regarding security reporting
As always, we ask that potential security issues be reported via private email to firstname.lastname@example.org, and not via Django's Trac instance or the django-developers list. Please see our security policies for further information.