● High · CVSS 7.5

How to Fix CVE-2026-25673: Denial of service via resource consumption in Django

Q: What is the CVSS score for CVE-2026-25673?

7.5 (High). Vector: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`.

Q: Where is the official advisory for CVE-2026-25673?

The vendor advisory is at [https://docs.djangoproject.com/en/dev/releases/security/](https://docs.djangoproject.com/en/dev/releases/security/). The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-25673.

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-25673 is a denial of service via resource consumption in djangoproject Django. The fix is to upgrade to Django 4.2.29; Django 5.2.12; Django 6.0.3.

⚡ At a glance


Severity	7.5 (High)
Actively exploited?	No public listing in CISA KEV
Affected	Django 6.0 to <6.0.3; Django 5.2 to <5.2.12; Django 4.2 to <4.2.29
Fixed in	Django 4.2.29; Django 5.2.12; Django 6.0.3
Type (CWE)	CWE-400: Uncontrolled Resource Consumption

What is CVE-2026-25673?

An issue was discovered in 6.0 before 6.0.3, 5.2 before 5.2.12, and 4.2 before 4.2.29.

URLField.to_python() in Django calls urllib.parse.urlsplit(), which performs NFKC normalization on Windows that is disproportionately slow for certain Unicode characters, allowing a remote attacker to cause denial of service via large URL inputs containing these characters.

Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.

Django would like to thank Seokchan Yoon for reporting this issue. The CVSS base score is 7.5 (High), which puts this in the upper risk band and warrants a fast patch cycle. The official advisory is at https://docs.djangoproject.com/en/dev/releases/security/.

Am I affected?

Check the version of Django you are running and compare it against the Affected row above (Django 6.0 to <6.0.3; Django 5.2 to <5.2.12; Django 4.2 to <4.2.29). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


# Linux package check
dpkg -s django 2>/dev/null | grep -i ^Version
rpm -q django 2>/dev/null
command -v django >/dev/null && django --version 2>/dev/null


# Windows (PowerShell)
Get-Package -Name "*Django*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "Django" 2>$null

How to fix CVE-2026-25673

Upgrade Django to a patched build: Django 4.2.29; Django 5.2.12; Django 6.0.3. The vendor advisory is the source of truth for the exact fixed version.

Ubuntu / Debian


sudo apt-get update
sudo apt-get install --only-upgrade django
dpkg -s django | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --refresh django -y
# or for older releases:
sudo yum update django -y
rpm -q django

SUSE / openSUSE


sudo zypper refresh
sudo zypper update django
rpm -q django

Python / pip


pip install --upgrade django
pip show django | grep -i version

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-25673 affecting Django
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-25673-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append

try {
    Write-Host "[1/4] Detect installed version"
    $pkg = Get-Package -Name "*Django*" -ErrorAction SilentlyContinue
    if ($pkg) { $pkg | Format-Table Name, Version }
    else { Write-Host "Not detected via Get-Package; try winget list" }

    Write-Host "[2/4] Backup configuration"
    $backup = "C:\Backup\django-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\Django" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to Django 4.2.29; Django 5.2.12; Django 6.0.3"
    winget upgrade --name "Django" --silent --accept-source-agreements --accept-package-agreements
    if ($LASTEXITCODE -ne 0) {
        # Fallback: pull latest via OS update channel
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verify the patched build"
    winget list --name "Django"
    Write-Host "Patch applied. Reboot if prompted."
    exit 0
} catch {
    Write-Error "Patch failed: $_"
    exit 1
} finally {
    Stop-Transcript
}

Complete Bash remediation script (Linux)


#!/usr/bin/env bash
# Fix script for CVE-2026-25673 affecting Django
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-25673-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
    dpkg -s django 2>/dev/null | grep -i ^Version || echo "django not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q django || echo "django not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-25673-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/django /etc/django.d /etc/django.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Apply the upgrade (target: Django 4.2.29; Django 5.2.12; Django 6.0.3)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y django
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y django
elif command -v yum >/dev/null; then
    yum update -y django
elif command -v zypper >/dev/null; then
    zypper --non-interactive update django
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s django 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q django
fi
echo "Done. Restart any service that loaded the old library."

If you can't patch immediately

Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.

Restrict exposure with nftables (Linux)


# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Block at the host firewall (Windows)


New-NetFirewallRule -DisplayName "Block-CVE-2026-25673" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-25673"

Disable the affected service (Linux)


sudo systemctl stop django 2>/dev/null || true
sudo systemctl disable django 2>/dev/null || true

If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.

How to verify the fix worked

After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.


# Linux
dpkg -s django 2>/dev/null | grep -i ^Version
rpm -q django 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true


# Windows
Get-Package -Name "*Django*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above Django 4.2.29; Django 5.2.12; Django 6.0.3. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-6609: Improper authorization in DjangoBlog — Improper authorization in DjangoBlog
How to Fix CVE-2026-1287: SQL Injection in Django — SQL Injection in Django
How to Fix CVE-2026-1312: SQL Injection in Django , SQL Injection in Django
How to Fix CVE-2026-35192: Use of Persistent Cookies Containing Sensitive Information in Django , Use of Persistent Cookies Containing Sensitive Information in Django
How to Fix CVE-2026-3902: ASGI header spoofing via underscore/hyphen conflation in Django , ASGI header spoofing via underscore/hyphen conflation in Django

Is CVE-2026-25673 actively exploited?

There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.

Do I need to reboot after patching CVE-2026-25673?

For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.

What is the CVSS score for CVE-2026-25673?

7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Where is the official advisory for CVE-2026-25673?

The vendor advisory is at https://docs.djangoproject.com/en/dev/releases/security/. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-25673.

References

Official vendor advisory: https://docs.djangoproject.com/en/dev/releases/security/
NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25673
CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
Additional reference: https://groups.google.com/g/django-announce
Additional reference: https://www.djangoproject.com/weblog/2026/mar/03/security-releases/

*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*