Live › vulnerability › CVE-2026-113733
Django's admin does not hide the password field on some user models, so staff users with only view permission can see full password hashes on the read-only change form. An attacker who holds such a staff account can take the hashes offline and try to crack them.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-03 16:21 UTC. All times on this page are UTC.
Only sites running Django 6.1 before 6.1.3 or 6.0 before 6.0.10 that use the admin site with staff accounts that have view permission on user models. The exposure depends on a non-default user model or on the password field being inherited through multi-table inheritance. Sites without the Django admin, or with no staff users holding view permissions on user models, are unlikely to be affected.
No product ranges from the sources yet.
python -m django --version and compare against the fixed ranges below.AUTH_USER_MODEL inherits its password field from a concrete parent model via multi-table inheritance.6.1.3 or later.6.0.10 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
An issue was discovered in Django 6.1 before 6.1.3 and 6.0 before 6.0.10.
The django.contrib.admin.utils.display_for_field() function did not obfuscate the password field of user models other than AUTH_USER_MODEL, or of an AUTH_USER_MODEL inheriting its password field from a concrete parent model through multi-table inheritance, which allows authenticated staff users with only the view permission on such a model to obtain full password hashes via the read-only change form.
Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected.
Django would like to thank Aaron chen for reporting this issue.
This page as .md · .json · in your agent: get_signal("CVE-2026-113733")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.