CVE-2026-83805
Received Received - Intake

Approval Workflow Forgery in Nautobot

Vulnerability report for CVE-2026-83805, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-22

Last updated on: 2026-09-22

Assigner: GitHub, Inc.

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-22
Last Modified
2026-09-22
Generated
2026-09-23
AI Q&A
2026-09-22
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
nautobot nautobot 3.0
nautobot nautobot 3.1
nautobot nautobot 3.1.8

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-285 The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is an authorization bypass in Nautobot's approval workflow REST API. It allows users with the extras.add_approvalworkflowstageresponse permission to self-approve and bypass legitimate approval checks without proper authorization enforcement.

Detection Guidance

Check Nautobot versions between 3.0.0 and 3.1.7 for unauthorized approval workflow responses. Review logs for suspicious API calls to the ApprovalWorkflowStageResponse endpoint with extras.add_approvalworkflowstageresponse permission. Look for responses marked as approved by users who lack proper approver-group membership or change permissions.

Impact Analysis

An attacker could exploit this to set approval responses to approved, attribute them to arbitrary users, and trigger job activation through the workflow's approval cascade. This could lead to unauthorized activation of scheduled jobs and potential data integrity impacts.

Compliance Impact

This vulnerability allows unauthorized users to approve workflows and activate scheduled jobs without proper permissions, which could lead to unauthorized changes in network configurations or data processing. Such unauthorized actions may violate compliance requirements for data integrity and access controls under standards like GDPR and HIPAA.

Mitigation Strategies

Upgrade Nautobot to version 3.1.8 or later to patch the vulnerability. Restrict the extras.add_approvalworkflowstageresponse permission to only trusted users. Monitor approval workflows for unauthorized approvals or job activations.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-83805. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart