Vulnerability in djangoproject Django

[ Description ]Official description

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.

[ Fixes ]Fixes and patches

No fix or interim patch is linked from our sources yet. Check the vendor references below and limit exposure of affected systems until a fix is available.

[ Advisories ]Government CERT advisories

• BSI CERT-Bund3 Nov 2026WID-SEC-2026-4333

  Django: Multiple vulnerabilities Translated from German

  Risk mediumCVE-2026-113593CVE-2026-114582CVE-2026-111362+3 more CVEs

[ References ]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