Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-44794 medium CVSS 5.4

Vulnerability in nautobot (CVE-2026-44794)

Summary

Vulnerability in nautobot (CVE-2026-44794). Risk of unauthorized operations or information disclosure. Exploitable via GenericForeignKey. Mitigation: upgrade to 2.4.33 or later.

Original description

The description as published by the source.

Impact

In the case of inter-object references via GenericForeignKey (a pattern allowing an object to reference another object that may belong to one of several different "content types" or database tables), when creating or updating an object containing a GenericForeignKey, Nautobot's REST API failed to enforce user "view" permissions when determining whether a given reference to another object would be valid.

As a concrete example, a user:

  • who has permission to create or update ImageAttachment records
  • but who lacks permission to view (some or all) Device records
  • but who knows (via some other mechanism) the UUID of a specific Device that they do not otherwise have access to

could create via the REST API an ImageAttachment linked to that specific Device.

Other models that use GenericForeignKey and may be writable via the REST API, and hence have a similar vulnerability to ImageAttachment, may include:

  • ApprovalWorkflow
  • Cable
  • ConfigContext
  • ContactAssociation
  • DataCompliance
  • Device
  • ExportTemplate
  • GraphQLQuery
  • Note
  • ObjectMetadata
  • RelationshipAssociation
  • StaticGroupAssociation
  • VirtualMachine

Additionally, any Nautobot Apps that provide models with a REST API and use GenericForeignKey may have a similar vulnerability for their models.

Patches

A general-purpose fix has been implemented in Nautobot 2.4.33 and 3.1.2, which ensures correct application of "view" permissions when creating or mod…

Source: GitHub Security Advisories (Global) 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-44794 has been found in nautobot.
Attackers can target a specific entry point like GenericForeignKey over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade nautobot to 2.4.33 or later.
If unsure, ask your IT team or search "nautobot CVE-2026-44794" on the vendor's site.

CVE-2026-44794 (nautobot) — CWE-862 / CVSS v3 5.4
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GenericForeignKey / ImageAttachment / Device / ApprovalWorkflow
Patched: 2.4.33 — apply immediately
Workaround: No known workarounds at this time.
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-862) exists in nautobot. Attackers reach the vulnerable code path via GenericForeignKey.

📍 Affected scope

Check the vendor advisory for the affected versions of nautobot. Attack surface: GenericForeignKey / ImageAttachment / Device / ApprovalWorkflow.

🔥 Severity

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

🔧 How to fix

Update to 2.4.33.

🛡️ Workaround

Workaround: No known workarounds at this time.

🔍 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 
    No known workarounds at this time.

    パッチが適用されるまでの応急処置として、No known workarounds at this time. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade nautobot to 2.4.33

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

  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":"2.4.33"}]}]
PyPI nautobot
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.4.33"}]}]

References

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