CVE-2026-113733

Password hash disclosure to "view only" admin users with custom user models

  • Low 2.2

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.

Key facts

Published
3 Nov 2026
Last changed
3 Nov 2026
Assigned by
DSF
EPSS
0.392% likely to be exploited in the next 30 days, higher than 33.88% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 2.2CVSS 3.1, Lowfrom the CNA (DSF)CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N
  • 2.1CVSS 4.0, Lowfrom the CNA (DSF)CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

CAPEC-116: Excavation (CNA impact statement)

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
djangoprojectDjango
  • Default status: unaffected
  • 6.1 up to but excluding 6.1.3 (affected)
  • 6.1.3 (unaffected)
  • 6.0 up to but excluding 6.0.10 (affected)
  • 6.0.10 (unaffected)

Timeline

  1. 7 Oct 2026 Initial report received.
  2. 23 Oct 2026 Vulnerability confirmed.
  3. 3 Nov 2026 Security release issued.
  4. 3 Nov 2026 Published

Weakness

References