Is CVE-2026-4277 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-4277 being exploited in the wild.

How severe is CVE-2026-4277?

Critical severity, with a CVSS score of 9.8, published 7 April 2026.

Which products and versions are affected?

Django (PyPI) ECOSYSTEM:introduced=4.2,fixed=4.2.30,introduced=5.2,fixed=5.2.13,introduced=6.0,fixed=6.0.4, ECOSYSTEM:introduced=6.0,fixed=6.0.4.

Is there a fix for CVE-2026-4277?

Yes. Django (PyPI): upgrade to 6.0.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-4277 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-4277?

Check whether you run Djangoproject Django or Django (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-4277: Django missing authorization in GenericInlineModelAdmin

CVE-2026-4277 · Severity: critical · CVSS 9.8 · Published 2026-04-07

Django is a popular web framework used to build and manage websites. A security flaw in its administrative interface could allow a user with limited access to add new data records they are not authorized to create. This occurs because the system fails to properly check permissions when receiving specifically crafted web requests, potentially leading to unauthorized data entry.

Technologies: Djangoproject Django, Django (PyPI). Vendors: Djangoproject, PyPI.

Quick answers

Is CVE-2026-4277 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-4277 being exploited in the wild.
How severe is CVE-2026-4277?: Critical severity, with a CVSS score of 9.8, published 7 April 2026.
Which products and versions are affected?: Django (PyPI) ECOSYSTEM:introduced=4.2,fixed=4.2.30,introduced=5.2,fixed=5.2.13,introduced=6.0,fixed=6.0.4, ECOSYSTEM:introduced=6.0,fixed=6.0.4.
Is there a fix for CVE-2026-4277?: Yes. Django (PyPI): upgrade to 6.0.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-4277 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-4277?: Check whether you run Djangoproject Django or Django (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Django (PyPI): upgrade to 6.0.4 or later
```
pip install "Django>=6.0.4"
```

Technical details

A vulnerability classified as Missing Authorization (CWE-862) exists in Django's GenericInlineModelAdmin. The component fails to validate 'add' permissions when processing forged POST data for inline model instances. An attacker with low-level administrative privileges can exploit this by submitting crafted requests to create model instances they should not have permission to add. The issue affects Django versions 6.0.x, 5.2.x, and 4.2.x, and has been addressed in versions 6.0.4, 5.2.13, and 4.2.30.

Affected products

Django Software Foundation Django >= 6.0, < 6.0.4
Django Software Foundation Django >= 5.2, < 5.2.13
Django Software Foundation Django >= 4.2, < 4.2.30

Identifiers

CVE-2026-4277
GHSA-pwjp-ccjc-ghwg
PYSEC-2026-52

Timeline

2026-04-07: disclosed
2026-04-07: advisory
2026-04-07: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.