CVE-2026-44797 Details
Description
Nautobot is a Network Source of Truth and Network Automation Platform. Prior to 2.4.33 and 3.1.2, 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). This vulnerability is fixed in 2.4.33 and 3.1.2.
A server-side request forgery (SSRF) vulnerability has been identified in Nautobot versions prior to 2.4.33 and 3.1.2. This vulnerability allows users with sufficient access to configure webhooks that can send requests to hosts and IP addresses that should be blocked. The issue arises from the webhook data model's flexibility, which could be exploited to perform unauthorized requests.
Users can update to Nautobot versions 2.4.33 or 3.1.2, where this vulnerability has been fixed. After updating, administrators should review and audit existing webhook records to ensure they comply with the new security measures.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed May 29, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-918 | Server-Side Request Forgery (SSRF) | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| networktocode nautobot | < 2.4.33 >= 3.0.0, < 3.1.2 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 14, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| May 29, 2026 | Initial Analysis | [email protected] |
| May 28, 2026 | New CVE Received | [email protected] |