Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-83805 medium CVSS 6.4

Vulnerability in nautobot (CVE-2026-83805)

Summary

Vulnerability in nautobot (CVE-2026-83805). Risk of unauthorized operations or information disclosure. Exploitable via change. Mitigation: upgrade to 3.1.8 or later.

Original description

The description as published by the source.

Impact

This is an authorization bypass that escalates into unauthorized server-side job execution.

  1. Primary impact - self-approval: The approver checks (approver-group membership, change permission on the object under review, one-response-per-user) are enforced only in the approve/deny actions on ApprovalWorkflowStage. The generic ApprovalWorkflowStageResponse create endpoint enforces none of them, so a user holding only extras.add_approvalworkflowstageresponse can POST approved responses directly and drive a stage past its min_approvers threshold with no legitimate approver involved. The serializer also exposes user and state as writable, letting the attacker attribute responses to arbitrary users.

  2. Escalated impact job activation: Because the approval workflow gates a ScheduledJob, self-approval does not stop at the approval record. Stage approval cascades through ApprovalWorkflow.save() to on_workflow_approved(), which sets the target job to enabled/active.

Patches

Fixed in Nautobot v3.1.8

Workarounds

Restrict the extras.add_approvalworkflowstageresponse permission so that no untrusted user holds it; approval responses should only ever be created via the stage approve/deny actions. There is no configuration flag that disables the generic create endpoint prior to the patch.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-83805 has been found in nautobot.
Attackers can target a specific entry point like change over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.4/10.
What to do: upgrade nautobot to 3.1.8 or later.
If unsure, ask your IT team or search "nautobot CVE-2026-83805" on the vendor's site.

CVE-2026-83805 (nautobot) — CWE-285 / CVSS v3 6.4
Attack vector: remote (network-reachable) / no user interaction
Attack surface: change / approve / deny / ApprovalWorkflowStage
Patched: 3.1.8 — apply immediately
Workaround: Restrict the extras.add_approvalworkflowstageresponse permission so that no untrusted user holds it; approval responses should only ever be created via the stage approve/deny actions.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-285) exists in nautobot. Attackers reach the vulnerable code path via change.

📍 Affected scope

Check the vendor advisory for the affected versions of nautobot. Attack surface: change / approve / deny / ApprovalWorkflowStage.

🔥 Severity

Severity: Medium (CVSS 6.4/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 3.1.8.

🛡️ Workaround

Workaround: Restrict the extras.add_approvalworkflowstageresponse permission so that no untrusted user holds it; approval responses should only ever be created via the stage approve/deny actions.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'nautobot' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'nautobot' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で nautobot を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    Restrict the `extras.add_approvalworkflowstageresponse` permission so that no untrusted user holds it; approval responses should only ever be created via the stage `approve`/`deny` actions.

    パッチが適用されるまでの応急処置として、Restrict the extras.add_approvalworkflowstageresponse permission so that no untrusted user holds it; approval responses should only ever be created via the stage approve/deny actions. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade nautobot to 3.1.8

    ステージング環境で 3.1.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip nautobot
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.8"}]}]
PyPI nautobot
[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.1.8"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details