# 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...

Advisory record · `GHSA-wqfg-m96j-85vm`

- **Identifiers:** `GHSA-wqfg-m96j-85vm` · `BIT-django-2025-27556` · `CVE-2025-27556` · `PYSEC-2025-14`
- **State:** Confirmed
- **Severity:** CVSS 5.8 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-770](https://cwe.mitre.org/data/definitions/770.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 2 Apr 2025
- **Updated:** 10 Jun 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 2 Apr 2025, 13:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `django` (PyPI): affected `>=5.0, <5.0.14 || >=5.1, <5.1.8`; fixed in `5.0.14`, `5.1.8`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Django versions 5.0 before 5.0.14 and 5.1 before 5.1.8 are vulnerable. On Windows, NFKC Unicode normalization is slow, so an attacker can send inputs containing a very large number of Unicode characters to django.contrib.auth.views.LoginView, LogoutView, or django.views.i18n.set_language to cause a denial of service. Upgrade to Django 5.0.14 or 5.1.8.

Written 10 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.8 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:L`, from CNA (mitre)

- **CISA KEV:** Not listed.
- **EPSS:** 0.011, the 65th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 2 Apr 2025. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-wqfg-m96j-85vm](https://github.com/advisories/GHSA-wqfg-m96j-85vm)
- [OSV: GHSA-wqfg-m96j-85vm](https://osv.dev/vulnerability/GHSA-wqfg-m96j-85vm)
- <https://www.djangoproject.com/weblog/2025/apr/02/security-releases/>
- <https://docs.djangoproject.com/en/dev/releases/security/>
- <https://groups.google.com/g/django-announce>
- <http://www.openwall.com/lists/oss-security/2025/04/02/2>
- <https://github.com/advisories/GHSA-wqfg-m96j-85vm>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-wqfg-m96j-85vm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-wqfg-m96j-85vm/>. Everything for agents: <https://agentprime.io/llms.txt>.
