Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-44797 high CVSS 8.5

SSRF (Server-Side Request Forgery) in nautobot (CVE-2026-44797)

Summary

SSRF in nautobot (CVE-2026-44797). Confidential information can be exposed externally. Exploitable via Webhook. Mitigation: upgrade to 2.4.33 or later.

Original description

The description as published by the source.

Impact

Nautobot's Webhook data model and associated feature set could be configured by users with sufficient access to perform requests to various hosts and IP addresses that should not be permitted, allowing for various behaviors similar to server-side request forgery (SSRF).

Patches

Fixes are available in Nautobot v2.4.33 and v3.1.2.

In support of this fix, three new settings variables have been added to Nautobot:

  • WEBHOOK_ALLOWED_SCHEMES - By default new or updated Webhook records will be restricted to HTTP or HTTPS only, disallowing other schemes that may have been previously allowed. Administrators should audit existing Webhook records to identify any that are invalid, and either update/delete said records or customize WEBHOOK_ALLOWED_SCHEMES as appropriate.
  • WEBHOOK_ADDITIONAL_BLOCKED_NETWORKS - This can be used to specify additional IP networks that should be denied to Webhook sending, for example some deployments may wish to disallow RFC1918 addresses or even disallow all networks and carve out specific exemptions using the following setting.
  • WEBHOOK_ALLOWED_HOSTS - This can be used to provide an allow-list of specific hosts that would otherwise be blocked by any WEBHOOK_ADDITIONAL_BLOCKED_NETWORKS configuration.

Workarounds

Administrators should review which users have been granted add or change permissions for the Webhook data model, and should review currently defined Webhook records for safety and validity. Other th…

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-44797 has been found in nautobot.
Attackers can target a specific entry point like Webhook over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.5/10.
What to do: upgrade nautobot to 2.4.33 or later.
If unsure, ask your IT team or search "nautobot CVE-2026-44797" on the vendor's site.

CVE-2026-44797 (nautobot) — CWE-918 / CVSS v3 8.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: Webhook / WEBHOOK_ALLOWED_SCHEMES / WEBHOOK_ADDITIONAL_BLOCKED_NETWORKS / WEBHOOK_ALLOWED_HOSTS
Patched: 2.4.33 — apply immediately
Workaround: Administrators should review which users have been granted add or change permissions for the Webhook data model, and should review currently defined Webhook records for safety and validity.
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

SSRF (CWE-918) exists in nautobot. Attackers reach the vulnerable code path via Webhook.

📍 Affected scope

Check the vendor advisory for the affected versions of nautobot. Attack surface: Webhook / WEBHOOK_ALLOWED_SCHEMES / WEBHOOK_ADDITIONAL_BLOCKED_NETWORKS / WEBHOOK_ALLOWED_HOSTS.

🔥 Severity

Severity: High (CVSS 8.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 2.4.33.

🛡️ Workaround

Workaround: Administrators should review which users have been granted add or change permissions for the Webhook data model, and should review currently defined Webhook records for safety and validity.

🔍 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 
    Administrators should review which users have been granted `add` or `change` permissions for the `Webhook` data model, and should review currently defined `Webhook` records for safety and validity.

    パッチが適用されるまでの応急処置として、Administrators should review which users have been granted add or change permissions for the Webhook data model, and should review currently defined Webhook records for safety and validity. を実施。回避策の副作用 (機能低下) を確認した上で。

  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