CVE-2026-4277
Djangoproject Django broken access control
- Published7 Apr 2026
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-4277 being actively exploited?
CVE-2026-4277 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.60%.
How severe is CVE-2026-4277?
CVE-2026-4277 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.60% probability of exploitation.
Which products are affected by CVE-2026-4277?
Affected products include Djangoproject Django.
How do I fix CVE-2026-4277?
Upgrade affected software to a fixed version, for example Djangoproject Django 4.2.30 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-4277 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.