CVE-2026-113733
An issue was discovered in Django 6.1 before 6.1.3 and 6.0 before …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- docs.djangoproject.com/en/dev/releases/security/
- github.com/django/django/commit/67cce9dcd23ddeec41ccf0abfe3431e3cd724365
- github.com/django/django/commit/7d875c0a49d2a59335c65f6bf57970a5bac03be2
- github.com/django/django/commit/f5b039a619b3b5394ea5b966e17c7546fda6f937
- groups.google.com/g/django-announce
- www.djangoproject.com/weblog/2026/nov/03/security-releases/
- nvd.nist.gov/vuln/detail/CVE-2026-113733
- cve.org/CVERecord?id=CVE-2026-113733
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.