CVE-2025-32873: Django: Denial-of-service possibility in strip_tags()

Published May 7, 2025
·
Updated

An issue was discovered in Django 4.2 before 4.2.21, 5.1 before 5.1.9, and 5.2 before 5.2.1. The django.utils.html.striptags() function is vulnerable to a potential denial-of-service (slow performance) when processing inputs containing large sequences of incomplete HTML tags. The template filter striptags is also vulnerable, because it is built on top of striptags().

Affected Software

12 affected componentsFixes available
Django Django
pip/django>=5.2<5.2.1
5.2.1
pip/django>=5.1<5.1.9
5.1.9
pip/django>=4.2<4.2.21
4.2.21
djangoproject Django>=4.2.0<4.2.21
djangoproject Django>=5.1<5.1.9
djangoproject Django=5.2
alpine/py3-django<4.2.21-r0
4.2.21-r0
alpine/py3-django<4.2.21-r0
4.2.21-r0
alpine/py3-django<4.2.21-r0
4.2.21-r0
alpine/py3-django<4.2.21-r0
4.2.21-r0
debian/python-django
3:3.2.25-0+deb12u33:3.2.25-0+deb12u63:4.2.28-0+deb13u23:4.2.28-0+deb13u13:5.2.17-23:5.2.19-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/Django to a version that resolves this vulnerability.

    Fixed in 5.2.1
  2. Upgrade

    Upgrade pip/Django to a version that resolves this vulnerability.

    Fixed in 5.1.9
  3. Upgrade

    Upgrade pip/Django to a version that resolves this vulnerability.

    Fixed in 4.2.21
  4. Upgrade

    Upgrade alpine/py3-django to a version that resolves this vulnerability.

    Fixed in 4.2.21-r0
  5. Upgrade

    Upgrade debian/python-django to a version that resolves this vulnerability.

    Fixed in 3:3.2.25-0+deb12u3Fixed in 3:3.2.25-0+deb12u6Fixed in 3:4.2.28-0+deb13u2Fixed in 3:4.2.28-0+deb13u1Fixed in 3:5.2.17-2Fixed in 3:5.2.19-1
  6. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 4.2.21
  7. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 5.1.9
  8. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 5.2.1

Event History

May 8, 2025
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:17 AM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·04:17 AM
DescriptionSeverityAffected Software
Advisory Published
via GitHub·06:30 AM
Jun 3, 2025
Exploit Published
via GitHub·09:16 AM

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2025-32873?

The severity of CVE-2025-32873 is classified as high due to the potential for remote code execution.

2

How do I fix CVE-2025-32873?

To fix CVE-2025-32873, upgrade Django and the python-django package to the latest secure versions available for your distribution.

3

What versions of Django are affected by CVE-2025-32873?

CVE-2025-32873 affects Django versions 2.2.x up to 2.2.28 and several 3.x versions including 3.2.x prior to 3.2.19.

4

Is there a workaround for CVE-2025-32873?

While upgrading is strongly recommended, a potential workaround is to restrict access to the vulnerable application components.

5

What is the impact of CVE-2025-32873 on applications?

CVE-2025-32873 can allow an attacker to execute arbitrary code in the context of the web application, leading to data breaches or system compromise.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203