Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-4277: 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 inli

49
This month
CRITICAL 9.8REMOTEUPGRADE

CVE-2026-4277 is a critical-severity flaw (CVSS 9.8) affecting django. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • Critical severity
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score9.8 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.5% (top 61%)
CISA exploited listNo
WeaknessCWE-862
Published2026-04-07
Last modified2026-10-26
Publisher (CNA): Django Software Foundation · Vendor: djangoproject

Share: LinkedIn · X · Reddit

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

djangoproject django UPGRADE
Affected: >= 4.2 and < 4.2.30 · >= 5.2 and < 5.2.13 · >= 6.0 and < 6.0.4
Fixed in: 4.2.30, 5.2.13, 6.0.4
Safe to downgrade to: a release before 4.2
1. Check installed version
apt-cache policy django || rpm -q django || django --version
2. UPGRADE to 4.2.30 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade django
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade django
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 4.2 (Debian / Ubuntu)
apt-cache madison django sudo apt install django=<VERSION_BEFORE_4.2> sudo apt-mark hold django
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list django sudo dnf downgrade django-<VERSION_BEFORE_4.2> sudo dnf versionlock add django
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-4277?

django: upgrade to 4.2.30, 5.2.13, 6.0.4. Exact commands for each OS are on this page.

Is CVE-2026-4277 being exploited?

CVE-2026-4277 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-4277 affect?

CVE-2026-4277 affects django. Severity is critical (CVSS 9.8). 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 Djan

How urgent is CVE-2026-4277?

Priority 49/100. Critical severity; Remotely exploitable, no login, no user action

Software pages

Django vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.