Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2026-44797

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

Summary

SSRF in nautobot (CVE-2026-44797). Risk of unauthorized operations or information disclosure. Exploitable via ``Webhook``. Mitigation: upgrade to `2.4.33` or later.

AI summary snake-internal / snake-material-v2

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. Risk of unauthorized operations or information disclosure. CVSS score: ?/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 / 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`` without authentication.
📍 Affected scope
nautobot — . Attack surface: `Webhook` / `WEBHOOK_ALLOWED_SCHEMES` / `WEBHOOK_ADDITIONAL_BLOCKED_NETWORKS` / `WEBHOOK_ALLOWED_HOSTS`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 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 (7 steps)

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. 5
    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. 6
    Apply patch patch 
    Upgrade nautobot to 2.4.33

    ステージング環境で 2.4.33 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

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

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

Affected packages

pip nautobot
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.4.33"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →