CVE-2026-44797: Nautobot: Webhook definitions could be used for server-side request forgery (SSRF)
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.
Published May 13, 2026 · Updated Jun 9, 2026
Affected packages
nautobot
- Ecosystem
- PyPI
- Affected
- >= 3.0.0a2, < 3.1.2
- Fixed in
- 3.1.2
- Check
pip show nautobot
nautobot
- Ecosystem
- PyPI
- Affected
- < 2.4.33
- Fixed in
- 2.4.33
- Check
pip show nautobot
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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 updatedWebhookrecords will be restricted to HTTP or HTTPS only, disallowing other schemes that may have been previously allowed. Administrators should audit existingWebhookrecords to identify any that are invalid, and either update/delete said records or customizeWEBHOOK_ALLOWED_SCHEMESas appropriate.WEBHOOK_ADDITIONAL_BLOCKED_NETWORKS- This can be used to specify additional IP networks that should be denied toWebhooksending, 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 anyWEBHOOK_ADDITIONAL_BLOCKED_NETWORKSconfiguration.
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 than that, no specific workaround has been identified.
References
- 2.4.33 (patch)
- 3.1.2 (patch)
Credited to whatisproblem.
References
- https://github.com/nautobot/nautobot/security/advisories/GHSA-c35q-vxrp-ph26
- https://github.com/nautobot/nautobot/commit/16aa4aa9796ab7a31c4d615ec945e1f16d8c77c4
- https://github.com/nautobot/nautobot/commit/7324c8f0d8c7245fbc691e15d729adc2d2707d08
- https://github.com/nautobot/nautobot/releases/tag/v2.4.33
- https://github.com/nautobot/nautobot/releases/tag/v3.1.2
- https://nvd.nist.gov/vuln/detail/CVE-2026-44797
- https://github.com/advisories/GHSA-c35q-vxrp-ph26
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-83801
Nautobot: Stored cross-site scripting (XSS) in object create/edit form help text
medium5.4Sep 22, 2026CVE-2026-83805
Nautobot: Authorization bypass in approval workflow REST API allows self-approval and unauthorized activation of scheduled jobs
medium6.4Sep 22, 2026CVE-2026-44794
Nautobot: REST API permits creation of GenericForeignKey references to objects that the user should not be able to reference
medium5.4May 13, 2026CVE-2026-44796
Nautobot: Object bulk rename UI actions vulnerable to denial of service by crafted regular expression (REDoS)
medium6.5May 13, 2026CVE-2026-44798
Nautobot: GitRepository.current_head field should not be writable through REST API
high7.1May 13, 2026CVE-2026-34203
Nautobot: Management of users via REST API does not apply configured password validators
low2.7Mar 31, 2026
