Django releases security updates for six CVEs
Django security releases address multiple vulnerabilities including CVE-2026-108147, CVE-2026-111211, CVE-2026-111362, CVE-2026-113593, CVE-2026-113733, and CVE-2026-114582.
40
CVE-2026-113733
Password hash disclosure in Django admin for non-AUTH_USER_MODEL before 6.1.3
- CVSS 4.0
- 2.1 low
- EPSS
- —
- Published
- ·
- Modified
AI analysisSummaries by Vani AI
The django.contrib.admin.utils.display_for_field() function in Django does not obfuscate passwords for user models other than AUTH_USER_MODEL or those inheriting via multi-table inheritance. Authenticated staff users with only view permission on such models can access full password hashes via the read-only change form. This affects Django 6.1 before 6.1.3 and 6.0 before 6.0.10.
What to do: Upgrade Django to 6.1.3 or 6.0.10. No workaround mentioned.
| Product | Affected | Fixed in |
|---|---|---|
| Django | 6.1 before 6.1.3 and 6.0 before 6.0.10 | 6.1.3 and 6.0.10 |
Estimated exposure
No basis for an estimate.
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Description · NVD
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.
- Weakness
- CWE-522
- Vector
- 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X