Skip to main content
VulnerabilityPublished Updated

CVE-2026-4277: djangoproject Django · Missing Authorization

Affects djangoproject DjangoSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.8 Critical · fixed in 6.0.4 : patch djangoproject Django as a priority.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 6.0.4, 5.2.13, 4.2.30
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade Django and django/django and django to 6.0.4, 5.2.13 or 4.2.30.

Affected software

ProductAffectedFixed in
djangoprojectDjangoAffected
  • >=6.0 <6.0.4
Fixed in
  • 6.0.4
djangoprojectDjangoAffected
  • >=5.2 <5.2.13
Fixed in
  • 5.2.13
djangoprojectDjangoAffected
  • >=4.2 <4.2.30
Fixed in
  • 4.2.30
PyPIdjango/djangopkg:pypi/django/djangoOther threatsAffected
  • <4.2.30
  • <5.2.13
  • <6.0.4
Fixed in
  • 4.2.30
  • 5.2.13
  • 6.0.4
PyPIdjangopkg:pypi/djangoOther threatsAffected
  • >=6.0 <6.0.4
  • >=5.2 <5.2.13
  • >=4.2 <4.2.30
Fixed in
  • 6.0.4
  • 5.2.13
  • 4.2.30

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, restrict access to Django admin interfaces and validate user permissions carefully.

Description

An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Add permissions on inline model instances were not validated on submission of forged `POST` data in `GenericInlineModelAdmin`. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank N05ec@LZU-DSLab for reporting this issue.

References

Community reviews

Loading reviews…