CVE-2025-27556 json
Django Potential Denial of Service (DoS) on Windows
published 2025-04-02 19 mo ago modified 2026-09-08 2 mo ago also BIT-django-2025-27556 , EUVD-2025-9536 , GHSA-wqfg-m96j-85vm , PYSEC-2025-14
- cvss
- 5.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 65%
- public exploits
- 0
- none known
Summary
An issue was discovered in Django 5.1 before 5.1.8 and 5.0 before 5.0.14. The NFKC normalization is slow on Windows. As a consequence, django.contrib.auth.views.LoginView, django.contrib.auth.views.LogoutView, and django.views.i18n.set_language are subject to a potential denial-of-service attack via certain inputs with a very large number of Unicode characters.
Patch / fix
- pypi django 5.0.14, 5.1.8
- bitnami django 5.0.14, 5.1.8
- djangoproject Django 5.0.14, 5.1.8
- python-Django5 openSUSE Tumbleweed 5.2.16-1.1
- python-Django6 openSUSE Tumbleweed 6.0-1.1
- python-Django openSUSE Tumbleweed 5.1.8-1.1
opensuse advisories openSUSE-SU-2026:11270-1openSUSE-SU-2026:10005-1openSUSE-SU-2025:14986-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-27556 updated cvss 5.8
django: Django DoS Unicode Attack
-
Red Hat Ansible Automation Platform 2 automation-controller, ansible-automation-platform-24/lightspeed-rhel8, ansible-automation-platform-25/lightspeed-rhel8, ansible-automation-platform-26/lightspeed-rhel9, ansible-automation-platform-24/platform-resource-runner-rhel8 Red Hat Discovery 1 discovery/discovery-server-rhel9not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 19 mo ago
Exploit prediction
1.08% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:L |
| GitHub | 3.1 | 5.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:L |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | django | >=5.0, <5.0.14 >=5.1, <5.1.8 |
5.0.14 5.1.8 |
| bitnami | django | >=5.0.0, <5.0.14 >=5.1.0, <5.1.8 |
5.0.14 5.1.8 |
Affected products
- djangoproject Django
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
- Technology feeds
References
-
github.com
/django/django/commit/2cb311f7b069723027fb5def4044d1816d7d2afd
web
-
github.com
/django/django/commit/39e2297210d9d2938c75fc911d45f0e863dc4821
web
-
github.com
/django/django/commit/8c6871b097b6c49d2a782c0d80d908bcbe2116f1
web
-
github.com
/django/django/commit/edc2716d01a6fdd84b173c02031695231bcee1f8
web
-
docs.djangoproject.com
/en/dev/releases/security/
vendor-advisory, advisory, web
-
groups.google.com
/g/django-announce
web, vendor-advisory, advisory
-
djangoproject.com
/weblog/2025/apr/02/security-releases/
vendor-advisory, advisory, article
-
openwall.com
/lists/oss-security/2025/04/02/2
web, mailing-list, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-27556
advisory, web
-
docs.djangoproject.com
/en/dev/releases/security
web
-
github.com
/django/django
package
-
github.com
/pypa/advisory-database/tree/main/vulns/django/PYSEC-2025-14.yaml
web
-
djangoproject.com
/weblog/2025/apr/02/security-releases
web
-
github.com
/advisories/GHSA-wqfg-m96j-85vm
advisory
Sources
- CVE List CVE-2025-27556
- GitHub Advisory GHSA-wqfg-m96j-85vm
- NVD CVE-2025-27556
- OSV BIT-django-2025-27556
- OSV PYSEC-2025-14
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.