djangoproject · Django · published 2026-11-03
CVE-2026-113733Password hash disclosure to "view only" admin users with custom user models
Routine No exploitation evidence; EPSS 0.4%.
CVE-2026-113733 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 34% of all CVEs. This Django vulnerability: CVSS 2.1 (v4.0). Fixed upstream in Django 6.1.3, 6.0.10, 5.2.19; Ubuntu still has unfixed releases. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Django 6.1.3, 6.0.10, 5.2.19.
Linux distribution packages
If you run the distro’s package rather than an upstream build, this is the version to look for.
| Distro | Release | Package | Status |
|---|---|---|---|
| Debian | 13 trixie | python-django | Not affected |
| 12 bookworm | python-django | Not affected | |
| Ubuntu | 26.04 LTS | python-django | No fix yet |
| 24.04 LTS | python-django | No fix yet | |
| 22.04 LTS | python-django | No fix yet |
From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.
Patch events
Web frameworkDjango
Django security releases: 6.1.3, 6.0.10, 5.2.19
Upgrade to
6.1.36.0.105.2.19Why: Vendor security release for server software (most severe: CVE-2026-108147).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.4% (34th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 2.1 (v4.0)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 | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- djangoproject Django
6.1to before6.1.3(affected)6.1.3(unaffected)6.0to before6.0.10(affected)6.0.10(unaffected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.