The Quarterly Threat Landscape Report is out. See what attackers are targeting now.Read report
An issue was discovered in Django 2.0 before 2.0.3, 1.11 before 1.11.11, and 1.8 before 1.8.19. If django.utils.text.Truncator's chars() and words() methods were passed the html=True argument, they were extremely slow to evaluate certain inputs due to a catastrophic backtracking vulnerability in a regular expression. The chars() and words() methods are used to implement the truncatechars_html and truncatewords_html template filters, which were thus vulnerable.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Alpine Linux | — | Upgrade py3-djangoUpgrade py-django | Mar 14, 2018 | Mar 9, 2018 |
| Arch Linux | — | Upgrade to the latest version of Arch Linux | Jul 11, 2025 | Mar 9, 2018 |
| Debian | — | Upgrade python-django | Apr 2, 2018 | Mar 9, 2018 |
| Oracle Solaris | — | Upgrade library/python/django-27 to version 1.11.16-11.4.4.0.1.1.0 on Solaris 11.4Upgrade library/python/django to version 1.11.16-11.4.4.0.1.1.0 on Solaris 11.4 | Dec 17, 2018 | Mar 9, 2018 |
| Suse | — | Upgrade python-django | Mar 28, 2018 | Mar 9, 2018 |
| Ubuntu | — | Upgrade python3-djangoUpgrade python-django | Apr 25, 2018 | Mar 6, 2018 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub