CVE-2025-32873

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.strip_tags() 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 strip_tags().

Published: 2025-05-08 Last update: 2025-09-02 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-32873 is rated Low Risk (34.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.17%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-32873

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-04 0.02% 0.17% +0.14%
2 2025-11-21 0.10% 0.02% -0.08%
3 2025-11-18 — 0.10% —

Full EPSS history (4 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-32873

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 3.9 1.4 [email protected]
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 3.9 1.4 [email protected]

Weakness enumeration for CVE-2025-32873

GitHub Security Advisory for CVE-2025-32873

GHSA-8j24-cjrq-gr2m · Severity: medium · Ecosystem: pip — Django has a denial-of-service possibility in strip_tags()

OS Trackers for CVE-2025-32873

vendor priority summary link
alpine — CVE-2025-32873: 1 source package rows (py3-django); 3 state rows across 3 repos (3.21-community, 3.22-community, edge-community); fixed 3, open 0. https://security.alpinelinux.org/vuln/CVE-2025-32873
debian not yet assigned CVE-2025-32873 not yet assigned priority: Debian including 1 source packages (python-django), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-32873
gentoo normal CVE-2025-32873: 1 GLSA(s) (202509-03), 1 atom(s) (dev-python/django); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2025-32873
redhat medium — https://access.redhat.com/security/cve/CVE-2025-32873
suse medium CVE-2025-32873 severity moderate: SUSE including 10 source package names (python3-Django-2.2.28-bp156.9.1, python311-Django-4.2.11-150600.3.21.1, …), 13 product×package rows across 5 product lines (SUSE Linux Enterprise Module for Package Hub 15 SP6, SUSE Linux Enterprise Module for Package Hub 15 SP7, … (5 product lines)): Fixed 13. https://www.suse.com/security/cve/CVE-2025-32873/
ubuntu medium CVE-2025-32873 medium priority: Ubuntu including 1 source packages (python-django), 10 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): released 7, needs-triage 3. https://ubuntu.com/security/CVE-2025-32873

Affected software / configurations for CVE-2025-32873

Vendor Product Version Raw CPE
djangoproject django >= 4.2.0, < 4.2.21 cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:*
djangoproject django >= 5.1, < 5.1.9 cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:*
djangoproject django 5.2 cpe:2.3:a:djangoproject:django:5.2:*:*:*:*:*:*:*

References for CVE-2025-32873

cvelogic Threat Intelligence