dbcve.org
DjangoFramework / library · Djangoproject

CVE-2025-26699

HIGH · 7.5 CVSS v3.1 Published 2025-03-06
Fix available
A fix is available. Upgrade to 4.2.20 / 5.0.13 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The django.utils.text.wrap() function and wordwrap template filter contain a denial-of-service vulnerability when processing very long strings, likely due to inefficient algorithmic complexity (potentially O(n^2) behavior) that causes excessive CPU consumption.

MitigationUpgrade Django to version 5.1.7, 5.0.13, or 4.2.20 or later to patch the vulnerability. Avoid passing untrusted extremely long strings to wrap() or the wordwrap filter until patched.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DjangoFramework / library
Affected:>= 4.2, < 4.2.20>= 5.0, < 5.0.13>= 5.1, < 5.1.7
Debian LinuxOperating system
Affected:= 11.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Django version
    Run 'python -c "import django; print(django.get_version())"' or check your requirements.txt/dependencies
    Affected if Version is >= 4.2 and < 4.2.20, OR >= 5.0 and < 5.0.13, OR >= 5.1 and < 5.1.7
  2. Search for usage of django.utils.text.wrap()
    Search your codebase for imports or calls to 'django.utils.text.wrap' or '.wrap(' in Python files
    Affected if Code calls wrap() function with untrusted or potentially long string input
  3. Search for wordwrap template filter usage
    Search template files (.html) for '|wordwrap' filter usage, especially in templates that render user-generated content
    Affected if Templates use the wordwrap filter on strings that could be very long
  4. Identify data sources feeding wrap functions
    Review code paths where strings passed to wrap() or wordwrap originate (user input, API responses, file reads, database fields)
    Affected if Untrusted or arbitrarily long strings from users or external sources can reach these functions

Your environment is affected if Django version is within the vulnerable ranges AND your code passes untrusted or very long strings to django.utils.text.wrap() or the wordwrap template filter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.2.20 / 5.0.13 / 5.1.7 or later
Fixed in 4.2.205.0.135.1.7
Interim mitigation

Upgrade Django to version 5.1.7, 5.0.13, or 4.2.20 or later to patch the vulnerability. Avoid passing untrusted extremely long strings to wrap() or the wordwrap filter until patched.

Recommended fix High confidence

Django 4.2.20, 5.0.13, or 5.1.7 depending on your current major version branch

  1. Check the currently installed Django version using: pip show django or django-admin --version
  2. Determine which Django major version branch you're on (4.2, 5.0, or 5.1)
  3. For Django 4.2.x: Run pip install --upgrade 'Django>=4.2.20,<4.2.21' or pip install Django==4.2.20
  4. For Django 5.0.x: Run pip install --upgrade 'Django>=5.0.13,<5.0.14' or pip install Django==5.0.13
  5. For Django 5.1.x: Run pip install --upgrade 'Django>=5.1.7,<5.1.8' or pip install Django==5.1.7
  6. After upgrade, verify the fix by running: python -c "import django; print(django.get_version())"
  7. Update requirements.txt or Pipfile to pin the specific fixed version
  8. If using Debian 11.0 with system Django, apply Debian security updates or rebuild with fixed Django packages
Caveat Django patch releases (x.y.z where z>0) are typically backward compatible and contain only bug fixes and security patches; review release notes if upgrading across minor versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Django Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,320
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,712.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26699 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-26699 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data