Django
Library41.1Mdownloads / month
PyPI downloads, last 30 days (pypistats, mirrors excluded).
PyPI ↗ · as of 2 Nov 2026 · High confidence
Version split: unknown. No public source for this product.
CVE-2026-113733
Password hash disclosure to "view only" admin users with custom user models
No known exploitation. EPSS puts it in the 34th percentile. Fixed versions are out.
CVSS 3.12.2LowEPSS percentile34th0.4% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix1 product2 fixed builds listed below
No public exploit knownFix1 product2 fixed builds listed below
Check it yourself
Run the check e.g. OID 1.3.6.1.4.1.25623.1.0.180979
What to do
Find your product and version, then upgrade to the build on the right.
- djangoproject DjangoAffected: ≥ 6.1, < 6.1.3Upgrade to: 6.1.3Affected: ≥ 6.0, < 6.0.10Upgrade to: 6.0.10Stated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
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.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
EPSS34th
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.4% chance of exploitation activity in the next 30 days, which ranks it in the 34th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
5 events over 6 days, from the signal feeds we watch.
- OpenVAS check added
- Publishedweakness classified, att&ck mapped, record updated
Affected products
Scale
How widely the affected products are used. This is not a count of vulnerable hosts.
Estimate Public sources, each figure dated. How much of it is already patched is not known.
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N
Scored 2.2 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
- Privileges Required HighRequires admin or elevated privileges
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality LowSome restricted information is disclosed, but limited in scope
- Integrity NoneNo integrity impact
- Availability NoneNo availability impact
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Django, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI