CVE-2026-4277
Inline admin permissions bypass via forged POST in Django GenericInlineModelAdmin.
Is CVE-2026-4277 being exploited?
Not confirmed. CVE-2026-4277 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.46% probability of exploitation in the next 30 days.
How severe is CVE-2026-4277?
CVE-2026-4277 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-4277?
Yes. A fix has been recorded for CVE-2026-4277. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-4277 affect?
CVE-2026-4277 affects Django 6.0.x (<6.0.4), Django 5.2.x (<5.2.13), Django 4.2.x (<4.2.30). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-4277?
Upgrade to patched versions; test admin workflows.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Forged POST can add/modify inline model permissions in Django admin, enabling privilege escalation.
Immediate action required
- affected>= 6.0 and < 6.0.4
- affected>= 5.2 and < 5.2.13
- affected>= 4.2 and < 4.2.30
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.