Skip to main content
VulnerabilityPublished Updated

CVE-2025-26699: Django Vulnerable to Allocation of Resources Without Limits or Throttling

Affects DjangoSource GCVE Database

0
Compare

Not known to be exploited · CVSS 5.0 Medium : upgrade to 4.2.20 when convenient.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 3.1 base score
5.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.2.20, 5.0.13, 5.1.7
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Mar 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade Django to 4.2.20; Django to 5.0.13; Django to 5.1.7.

Affected software

ProductAffectedFixed in
PyPIDjangoAffected
  • >=4.2 <4.2.20
Fixed in
  • 4.2.20
PyPIDjangoAffected
  • >=5.0 <5.0.13
Fixed in
  • 5.0.13
PyPIDjangoAffected
  • >=5.1 <5.1.7
Fixed in
  • 5.1.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply the official patches by upgrading Django to versions 4.2.20, 5.0.13, or 5.1.7 or later. These versions contain fixes that address the resource exhaustion vulnerability. No additional mitigation is required if these versions are in use.

Description

Django versions prior to 4.2.20, 5.0.13, and 5.1.7 contain a vulnerability in the django.utils.text.wrap() method and the wordwrap template filter. This flaw allows a potential denial-of-service (DoS) attack when processing very long strings, leading to resource exhaustion. The issue is fixed in the specified patched versions.

References

Community reviews

Loading reviews…