CVE-2025-26699

An issue was discovered in Django 5.1 before 5.1.7, 5.0 before 5.0.13, and 4.2 before 4.2.20. The django.utils.text.wrap() method and wordwrap template filter are subject to a potential denial-of-service attack when used with very long strings.

Published: 2025-03-06 Last update: 2025-10-03 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-26699 is rated Low Risk (36.9/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.29%). 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-26699

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-04-14 1.60% 0.29% -1.31%
2 2026-03-04 1.39% 1.60% +0.20%
3 2026-03-01 — 1.39% —

Full EPSS history (32 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.0 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
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.1 1.4 [email protected]
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H 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:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2025-26699

GitHub Security Advisory for CVE-2025-26699

GHSA-p3fp-8748-vqfq · Severity: medium · Ecosystem: pip — Django vulnerable to Allocation of Resources Without Limits or Throttling

OS Trackers for CVE-2025-26699

vendor priority summary link
alpine — CVE-2025-26699: 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-26699
debian not yet assigned CVE-2025-26699 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-26699
gentoo normal CVE-2025-26699: 1 GLSA(s) (202509-03), 1 atom(s) (dev-python/django); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2025-26699
redhat medium — https://access.redhat.com/security/cve/CVE-2025-26699
suse medium — https://www.suse.com/security/cve/CVE-2025-26699/
ubuntu medium CVE-2025-26699 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 8, needs-triage 2. https://ubuntu.com/security/CVE-2025-26699

Affected software / configurations for CVE-2025-26699

Vendor Product Version Raw CPE
djangoproject django >= 4.2, < 4.2.20 cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:*
djangoproject django >= 5.0, < 5.0.13 cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:*
djangoproject django >= 5.1, < 5.1.7 cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:*
debian debian_linux 11.0 cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*

References for CVE-2025-26699

cvelogic Threat Intelligence