Nautobot is a Network Source of Truth and Network Automation Platform. From 3.0.0 until 3.1.8, the generic ApprovalWorkflowStageResponse create endpoint does not enforce approver-group membership, change permission on the object under review, or the one-response-per-user restriction applied by the intended approve and deny actions. A user with only extras.add_approvalworkflowstageresponse can submit approved responses directly, while writable user and state fields permit responses to be attributed to arbitrary users. These forged responses can satisfy min_approvers, approve the workflow, and activate its gated ScheduledJob without a legitimate approver. This issue is fixed in version 3.1.8.
CVE-2026-83805
MEDIUMPre-NVD 6.46.4—Trending — 3 sources updated this week
EchelonGraph scoreMEDIUM confidence
This medium-severity CVE scores 6.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 78% 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: epss, secondary
6.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.4Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.4
- EG Score
- 6.4(medium)
- EG Risk
- 33(Track)EG Risk 33/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 computedSeverity64% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 22%
- KEV
- Not listed
Published
September 22, 2026
Last Modified
September 23, 2026
Advisory Details (3)
Auto-updated Sep 22, 2026Patch available. Sources: github_release, github, github_commit.
github_release Patch Available
v3.1.8 - 2026-07-17
Patch available: nautobot/nautobot v3.1.8
https://github.com/nautobot/nautobot/releases/tag/v3.1.8github_commit
commit 8682707d0391 (nautobot/nautobot)
Fix landed in nautobot/nautobot commit 8682707d0391 — awaiting tagged release
https://github.com/nautobot/nautobot/commit/8682707d0391cbfd7694e3276127b78dc9cf29d8github Patch Available
Authorization bypass in approval workflow REST API allows self-approval and unauthorized activation of scheduled jobs · Advisory · nautobot/nautobot · GitHub
https://github.com/nautobot/nautobot/security/advisories/GHSA-q4c5-2j6f-r476Vendor Advisories for CVE-2026-83805(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nautobot | 3.0.0 ... 3.1.7 (25 versions) | 3.1.8 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× 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.
- 2026-09-23 18:25 UTCEG score recompute
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-22 20:32 UTCEG score recompute
- 2026-09-22 19:53 UTCEG score recompute
- 2026-09-22 19:52 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-83805?
CVE-2026-83805 is a medium vulnerability published on September 22, 2026. Nautobot is a Network Source of Truth and Network Automation Platform. From 3.0.0 until 3.1.8, the generic ApprovalWorkflowStageResponse create endpoint does not enforce approver-group membership, change permission on the object under review, or the one-response-per-user restriction applied by the…
When was CVE-2026-83805 disclosed?
CVE-2026-83805 was first published in the National Vulnerability Database on September 22, 2026, with the most recent update on September 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-83805 actively exploited?
CVE-2026-83805 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 77.7% of all scored CVEs.
What is the CVSS score of CVE-2026-83805?
CVE-2026-83805 has a CVSS v3 base score of 6.4 (NVD).
How do I remediate CVE-2026-83805?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-83805, 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-83805
Is Your Infrastructure Affected by CVE-2026-83805?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.