CVE-2026-4277

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.8 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.5% (40th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from CISA-ADP (Vulnrichment) CVSS v3.1
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS

Also known asEUVD-2026-19687 (ENISA EUVD) · GHSA-pwjp-ccjc-ghwg (GitHub Security Advisories) · PYSEC-2026-52 (OSV.dev)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.8Exploit: None knownExposed services: Not assessed

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.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
40th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.CISA-ADP (Vulnrichment) CVSS v3.1 · CVSS v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 7, 2026

Last Modified

October 26, 2026

Advisory Details (3)

Auto-updated Nov 7, 2026
Patch available.
Web page

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/
Web page

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(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupython3-django (1.8.7-1ubuntu5.15+esm12) @ xenial2026-11-12ubuntu
ubuntupython3-django (3:5.2.4-1ubuntu2.4) @ questing2026-11-12ubuntu
pipDjango @ 6.0.4 (fixes >= 6.0, < 6.0.4)—ghsa
pipDjango @ 5.2.13 (fixes >= 5.2, < 5.2.13)—ghsa
pipDjango @ 4.2.30 (fixes >= 4.2, < 4.2.30)—ghsa

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

(7 across 7 ecosystems)
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
py3-django—
  • every version up to 4.2.30-r0: fixed in 4.2.30-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
py3-django—
  • every version up to 5.2.13-r0: fixed in 5.2.13-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
python-django2:2.2.24-1 ... 3:6.1~rc1-1 (184 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python-django3:3.2.19-1 ... 3:6.1~rc1-1 (114 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-django3:4.2.23-1 ... 3:6.1~rc1-1 (67 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-django3:4.2.23-1 ... 3:4.2.29-1 (9 versions)
  • every version up to 3:4.2.30-1: fixed in 3:4.2.30-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
django4.2 ... 6.0.3 (47 versions)
  • 6.0 up to 6.0.4: fixed in 6.0.4
  • 5.2 up to 5.2.13: fixed in 5.2.13
  • 4.2 up to 4.2.30: fixed in 4.2.30
—

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 16× in last 7d / 61× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 331 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 231 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-4277?
CVE-2026-4277 is a critical-severity vulnerability; its CVE record was 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 made public?
CVE-2026-4277 was made public on April 7, 2026: that is the date its CVE record's CNA, Django Software Foundation, gives for when the vulnerability was made public. The CVE record itself was published on April 7, 2026. EchelonGraph's copy of the record carries a last-modified date of October 26, 2026; the record at its source may have been updated since.
Is CVE-2026-4277 actively exploited?
CVE-2026-4277 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-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?
A fix for CVE-2026-4277 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-4277 are linked in the Vendor Advisories panel on this page.

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.