Today the Django team issued multiple releases -- Django 1.4.20, 1.6.11,
1.7.7, and 1.8c1 -- as part of our security process. These releases address
a couple security issues, and we encourage all users to upgrade as soon as
possible.
More details can be found on our blog:
https://www.djangopro
Today the Django team is issuing multiple releases -- Django 1.4.18, Django
1.6.10, and Django 1.7.3 -- as part of our security process. These releases
address several security issues, and we encourage all users to upgrade as
soon as possible.
More details can be found on our blog:
https://www
Earlier today a message posted to the django-developers mailing list
publicly disclosed what was later determined to be an exploitable security
issue in Django.
As such, we have short-circuited our normal one-week process and moved to
immediately issuing new releases to remedy the problem.
Full d
Today the Django team is issuing multiple releases -- Django 1.4.7, Django
1.5.3, and Django 1.6 beta 3 -- as part of our security process. These
releases address a directory-traversal vulnerability in one of Django's
built-in template tags.
More details can be found on our blog:
https://www.djan
Hi folks --
Today the Django team is issuing multiple releases -- Django 1.4.6, Django
1.5.2, and Django 1.6 beta 2 -- as part of our security process. These
releases address two cross-site scripting (XSS) vulnerabilities: one in a
widget used by Django's admin interface, and one in a utility func
Today we've released Django 1.3.1 and Django 1.2.6 to deal with
several security issues reported to us. Details of these issues and
the releases, along with several important advisory notes, are
available in the blog post on djangoproject.com:
https://www.djangoproject.com/weblog/2011/sep/09/secur
