{"answers":{"affected":"3 open source packages ship an affected version, including nautobot.","exploited":"There is no known exploitation of CVE-2026-83805 in the wild and no public exploit code.","fix":"Upgrade nautobot to 3.1.8 or later.","what":"CVE-2026-83805 is a medium-severity missing authorization vulnerability in nautobot, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-83805 and fix it if it is affected.\n\nWhat it is: CVE-2026-83805 is a medium-severity missing authorization vulnerability in nautobot, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-83805 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nautobot (PyPI): affected from 3.0.0; fixed in 3.1.8\n- nautobot (PyPI): affected from 3.0.0; fixed in 3.1.8\n- nautobot (PyPI): affected from 3.0.0; fixed in 3.1.8\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-83805/ (Markdown: https://insights.sbomify.com/CVE-2026-83805/index.md)","id":"CVE-2026-83805","markdown":"https://insights.sbomify.com/CVE-2026-83805/index.md","name":"CVE-2026-83805","record":{"aliases":["GHSA-q4c5-2j6f-r476","PYSEC-2026-4111"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Network automation platform","requires_auth":"low_privilege","summary":"Attackers can bypass approval workflows to self-approve and activate scheduled jobs, leading to unauthorized privilege escalation and data modification.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"},{"id":"CWE-285","name":"Improper Authorization"}],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Nautobot: Authorization bypass in approval workflow REST API allows self-approval and unauthorized activation of scheduled jobs","id":"CVE-2026-83805","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"Twisted: DNS Response Spoofing in twisted.names Due to Missing Source Address Validation","id":"CVE-2026-83813"},"packages":[{"ecosystem":"PyPI","fixed":["3.1.8"],"introduced":["3.0.0"],"last_affected":[],"package":"nautobot","purl":null,"source":"GHSA-q4c5-2j6f-r476"},{"ecosystem":"PyPI","fixed":["3.1.8"],"introduced":["3.0.0"],"last_affected":[],"package":"nautobot","purl":"pkg:pypi/nautobot","source":"GHSA-q4c5-2j6f-r476"},{"ecosystem":"PyPI","fixed":["3.1.8"],"introduced":["3.0.0"],"last_affected":[],"package":"nautobot","purl":"pkg:pypi/nautobot","source":"PYSEC-2026-4111"}],"prev":{"headline":"Sentry: Unsafe pickle deserialization in Relocation Feature","id":"CVE-2026-83803"},"products":["nautobot"],"published":"2026-09-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-26","vendors":["nautobot"]},"summary":"Attackers can bypass approval workflows to self-approve and activate scheduled jobs, leading to unauthorized privilege escalation and data modification.","url":"https://insights.sbomify.com/CVE-2026-83805/"}