Impact
Nautobot’s approval workflow REST API endpoint that creates approval workflow stage responses does not enforce approver group membership, required change permissions, or the one‑response‑per‑user rule. A user with the extras.add_approvalworkflowstageresponse permission can craft a response that indicates approval, set the responder field to any user, and provide the desired job state. This flaw allows attackers to satisfy the minimum number of approvers required by a workflow, consequently marking the workflow as approved and activating its gated ScheduledJob. The weakness is a classic example of improper authorization controls as described by CWE‑285 and a classic bypass of authentication logic in approval processes (CWE‑639).
Affected Systems
All Nautobot installations from version 3.0.0 through 3.1.7 are affected. The issue was fixed in Nautobot 3.1.8 and later. The vulnerable product is the Nautobot Network Source of Truth and Network Automation Platform.
Risk and Exploitability
The CVSS score of 6.4 indicates a medium impact. EPSS is not available, and the vulnerability is not listed in the CISA KEV catalog, suggesting no public exploit is known. The likely attack vector is a user who has API access and the extras.add_approvalworkflowstageresponse permission, either internally or from an external source with authenticated access. While the vulnerability requires no special network privilege, it can lead to unauthorized execution of scheduled automation tasks. The risk profile is moderate for environments where the affected permission is broadly distributed.
OpenCVE Enrichment
Github GHSA