Django security releases issued: 1.10 release candidate 1, 1.9.8, and 1.8.14
In accordance with our security release policy, the Django team is issuing Django 1.10 release candidate 1, Django 1.9.8 and 1.8.14. These release addresses a security issue detailed below. We encourage all users of Django to upgrade as soon as possible. The Django master branch is also updated.
Django 1.10 is now at release candidate stage. This marks the string freeze and the call for translators to submit translations. Provided no major bugs are discovered that can't be solved in the next two weeks, 1.10 final will be issued on or around August 1. Any delays will be communicated on the django-developers mailing list thread.
Affected supported versions
- Django master development branch
- Django 1.10 (now at release candidate status)
- Django 1.9
- Django 1.8
Per our supported versions policy, Django 1.7 and older are no longer receiving security updates.
Patches to resolve the issues have been applied to Django's master development branch and the 1.10, 1.9, and 1.8 release branches. The patches may be obtained from the following changesets:
- On the development master branch
- On the 1.10 release branch
- On the 1.9 release branch
- On the 1.8 release branch
The following new releases have been issued:
- Django 1.10rc1 (download Django 1.10rc1 | 1.10rc1 checksums)
- Django 1.9.8 (download Django 1.9.8 | 1.9.8 checksums)
- Django 1.8.14 (download Django 1.8.14 | 1.8.14 checksums)
The PGP key ID used for these releases is Tim Graham: 1E8ABDC773EDE252.
General notes regarding security reporting
As always, we ask that potential security issues be reported via private email to email@example.com, and not via Django's Trac instance or the django-developers list. Please see our security policies for further information.