CVE-2025-13473: Django has Observable Timing Discrepancy
Low
- OSV id
- GHSA-2mcm-79hx-8fxw
- Also known as
- BIT-django-2025-13473, CVE-2025-13473, PYSEC-2026-42
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| django PyPI |
>= 6.0a1, < 6.0.2 | 6.0.2 |
| django PyPI |
>= 5.2a1, < 5.2.11 | 5.2.11 |
| django PyPI |
>= 4.2a1, < 4.2.28 | 4.2.28 |
Versions we track that it affects: django 4.2.11; django 4.2.11; django 4.2.11
How to fix it
django (PyPI)
Upgrade django to 6.0.2 or later.
# in requirements.txt: change the line to django==6.0.2
pip install -r requirements.txt
- If it is an indirect dependency, upgrade the package that depends on it, or add a minimum version constraint for it (e.g. in constraints.txt, or as a dependency in pyproject.toml).
- Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
django (PyPI)
Upgrade django to 5.2.11 or later.
# in requirements.txt: change the line to django==5.2.11
pip install -r requirements.txt
- If it is an indirect dependency, upgrade the package that depends on it, or add a minimum version constraint for it (e.g. in constraints.txt, or as a dependency in pyproject.toml).
- Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
django (PyPI)
Upgrade django to 4.2.28 or later.
# in requirements.txt: change the line to django==4.2.28
pip install -r requirements.txt
- If it is an indirect dependency, upgrade the package that depends on it, or add a minimum version constraint for it (e.g. in constraints.txt, or as a dependency in pyproject.toml).
- Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
Not sure whether your project uses an affected version? Check your lockfile below for free.
Details
An issue was discovered in 6.0 before 6.0.2, 5.2 before 5.2.11, and 4.2 before 4.2.28.
The django.contrib.auth.handlers.modwsgi.check_password() function for authentication via mod_wsgi allows remote attackers to enumerate users via a timing attack. 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 Stackered for reporting this issue.
References
- GHSA-2mcm-79hx-8fxw on OSV.dev
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2025-13473
- Web: https://docs.djangoproject.com/en/dev/releases/security
- Package: https://github.com/django/django
- Web: https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2026-42.yaml
- Web: https://groups.google.com/g/django-announce
- Web: https://www.djangoproject.com/weblog/2026/feb/03/security-releases
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.