Vulnerability in Djangoproject Django

CVE-2026-113733

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.

Published · last modified .

CVSS v3 metric

CVSS v3 base score 2.2 (Low). Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N.

EPSS exploit prediction

No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.

Affected products

Weakness classification (CWE)

References

Frequently asked questions

What is CVE-2026-113733?
CVE-2026-113733 is a low-severity vulnerability in Djangoproject Django, classified under Insufficiently Protected Credentials. CVSS score: 2.2/10. Published 2026-11-03.
How severe is CVE-2026-113733?
Low severity. CVSS v3 base score is 2.2 out of 10.