CVE-2026-4277

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 62% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cisa-adp, epss
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

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 v3
9.8
EG Score
9.8(medium)
EG Risk
59(Track)
EG Risk 59/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
39%
KEV
Not listed

Published

April 7, 2026

Last Modified

June 23, 2026

Advisory Details (3)

Auto-updated Sep 13, 2026
No patch confirmed yet.
generic

Django security releases issued: 6.0.4, 5.2.13, and 4.2.30 | Weblog | Django

https://www.djangoproject.com/weblog/2026/apr/07/security-releases/
generic
https://groups.google.com/g/django-announce
generic

Archive of security issues | Django documentation | Django

https://docs.djangoproject.com/en/dev/releases/security/

Vendor Advisories for CVE-2026-4277(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3-django (1.8.7-1ubuntu5.15+esm12) @ xenial2026-06-12ubuntu
ubuntupython3-django (3:5.2.4-1ubuntu2.4) @ questing2026-06-12ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
python-django2:2.2.24-1 ... 3:6.1~rc1-1 (184 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
python-django3:3.2.19-1 ... 3:6.1~rc1-1 (108 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
python-django3:4.2.23-1 ... 3:6.1~rc1-1 (63 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-django3:4.2.23-1 ... 3:4.2.29-1 (9 versions)3:4.2.30-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
django4.2 ... 6.0.3 (47 versions)6.0.4—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 4× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 208 total refreshes for this CVE.

  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-11 14:53 UTCEPSS rescore
  3. 2026-09-10 09:35 UTCEPSS rescore
  4. 2026-09-08 22:01 UTCEPSS rescore
  5. 2026-09-07 16:01 UTCEPSS rescore
  6. 2026-09-06 13:47 UTCEPSS rescore
  7. 2026-09-04 05:06 UTCEPSS rescore
  8. 2026-09-02 20:10 UTCOSV refresh
  9. 2026-09-02 14:12 UTCEPSS rescore
  10. 2026-09-01 13:54 UTCEPSS rescore
  11. 2026-09-01 04:40 UTCEPSS rescore
  12. 2026-08-30 19:17 UTCEPSS rescore
  13. 2026-08-30 01:22 UTCEPSS rescore
  14. 2026-08-28 21:41 UTCEPSS rescore
  15. 2026-08-27 14:25 UTCEPSS rescore
  16. 2026-08-26 14:46 UTCEPSS rescore
  17. 2026-08-25 13:49 UTCEPSS rescore
  18. 2026-08-23 00:19 UTCEPSS rescore
  19. 2026-08-21 23:49 UTCEPSS rescore
  20. 2026-08-20 22:55 UTCEPSS rescore
  21. 2026-08-19 17:04 UTCEPSS rescore
  22. 2026-08-18 13:48 UTCEPSS rescore
  23. 2026-08-17 13:47 UTCEPSS rescore
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 11:54 UTCVendor advisory
Show 75 more
  1. 2026-08-16 08:17 UTCEG score recompute
  2. 2026-08-16 08:17 UTCVendor advisory
  3. 2026-08-16 02:14 UTCEPSS rescore
  4. 2026-08-15 01:30 UTCEPSS rescore
  5. 2026-08-14 23:32 UTCVendor advisory
  6. 2026-08-14 19:55 UTCVendor advisory
  7. 2026-08-14 16:18 UTCVendor advisory
  8. 2026-08-14 12:41 UTCVendor advisory
  9. 2026-08-14 09:04 UTCVendor advisory
  10. 2026-08-14 05:27 UTCEG score recompute
  11. 2026-08-14 05:27 UTCVendor advisory
  12. 2026-08-13 22:00 UTCEPSS rescore
  13. 2026-08-13 09:41 UTCVendor advisory
  14. 2026-08-13 02:54 UTCVendor advisory
  15. 2026-08-12 23:18 UTCVendor advisory
  16. 2026-08-12 19:41 UTCEG score recompute
  17. 2026-08-12 19:41 UTCVendor advisory
  18. 2026-08-12 13:51 UTCEPSS rescore
  19. 2026-08-11 23:30 UTCVendor advisory
  20. 2026-08-11 19:53 UTCEG score recompute
  21. 2026-08-11 19:53 UTCVendor advisory
  22. 2026-08-11 06:51 UTCVendor advisory
  23. 2026-08-11 03:15 UTCEG score recompute
  24. 2026-08-11 03:15 UTCVendor advisory
  25. 2026-08-11 00:00 UTCEPSS rescore
  26. 2026-08-10 11:56 UTCVendor advisory
  27. 2026-08-10 07:00 UTCVendor advisory
  28. 2026-08-10 03:23 UTCVendor advisory
  29. 2026-08-09 23:46 UTCVendor advisory
  30. 2026-08-09 20:09 UTCVendor advisory
  31. 2026-08-09 16:32 UTCEG score recompute
  32. 2026-08-09 16:32 UTCVendor advisory
  33. 2026-08-09 13:46 UTCEPSS rescore
  34. 2026-08-09 12:55 UTCVendor advisory
  35. 2026-08-09 08:35 UTCVendor advisory
  36. 2026-08-09 04:58 UTCEG score recompute
  37. 2026-08-09 04:58 UTCVendor advisory
  38. 2026-08-08 16:37 UTCEPSS rescore
  39. 2026-08-08 09:24 UTCVendor advisory
  40. 2026-08-08 05:47 UTCVendor advisory
  41. 2026-08-08 02:10 UTCVendor advisory
  42. 2026-08-07 22:33 UTCVendor advisory
  43. 2026-08-07 18:56 UTCEG score recompute
  44. 2026-08-07 18:56 UTCVendor advisory
  45. 2026-08-07 14:58 UTCVendor advisory
  46. 2026-08-06 17:36 UTCEG score recompute
  47. 2026-08-06 17:36 UTCVendor advisory
  48. 2026-08-06 13:47 UTCEPSS rescore
  49. 2026-08-06 12:59 UTCVendor advisory
  50. 2026-08-06 07:14 UTCVendor advisory
  51. 2026-08-06 03:37 UTCVendor advisory
  52. 2026-08-06 00:00 UTCEG score recompute
  53. 2026-08-06 00:00 UTCVendor advisory
  54. 2026-08-05 19:17 UTCEPSS rescore
  55. 2026-08-04 15:10 UTCEPSS rescore
  56. 2026-08-04 10:39 UTCEPSS rescore
  57. 2026-08-04 05:41 UTCVendor advisory
  58. 2026-08-04 02:01 UTCVendor advisory
  59. 2026-08-03 22:24 UTCEG score recompute
  60. 2026-08-03 22:24 UTCVendor advisory
  61. 2026-08-03 10:36 UTCEPSS rescore
  62. 2026-08-03 01:10 UTCVendor advisory
  63. 2026-08-02 21:33 UTCVendor advisory
  64. 2026-08-02 17:56 UTCVendor advisory
  65. 2026-08-02 14:19 UTCEG score recompute
  66. 2026-08-02 14:19 UTCVendor advisory
  67. 2026-08-02 02:27 UTCEPSS rescore
  68. 2026-08-01 04:16 UTCEPSS rescore
  69. 2026-07-30 16:28 UTCEPSS rescore
  70. 2026-07-30 01:30 UTCEPSS rescore
  71. 2026-07-28 15:37 UTCEPSS rescore
  72. 2026-07-26 14:54 UTCEPSS rescore
  73. 2026-07-25 14:18 UTCEPSS rescore
  74. 2026-07-24 14:18 UTCEPSS rescore
  75. 2026-07-23 14:18 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-4277?
CVE-2026-4277 is a critical vulnerability published on April 7, 2026. 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…
When was CVE-2026-4277 disclosed?
CVE-2026-4277 was first published in the National Vulnerability Database on April 7, 2026, with the most recent update on June 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-4277 actively exploited?
CVE-2026-4277 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 61.4% of all scored CVEs.
What is the CVSS score of CVE-2026-4277?
CVE-2026-4277 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-4277?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-4277, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-4277

Explore →

Is Your Infrastructure Affected by CVE-2026-4277?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs