Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.5amended

Nautobot: Webhook definitions could be used for server-side request forgery (SSRF)

CVE-2026-44797GHSA-c35q-vxrp-ph26

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (nautobot 3.1.2, 2.4.33), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI nautobot

    Affected
    >= 3.0.0a2, < 3.1.2< 2.4.33
    Fixed in
    3.1.2, 2.4.33

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N
EPSS
  • CVE-2026-44797: 0.24% estimated exploitation activity in the next 30 days; percentile 14.57 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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: - WEBHOOKALLOWEDSCHEMES - 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 WEBHOOKALLOWEDSCHEMES as appropriate. - WEBHOOKADDITIONALBLOCKEDNETWORKS - 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-c35q-vxrp-ph26

  2. Revision 1 · created ·

    Published from osv record GHSA-c35q-vxrp-ph26

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-44797

Advisory: Nautobot: Webhook definitions could be used for server-side request forgery (SSRF)
IDs: CVE-2026-44797, GHSA-c35q-vxrp-ph26
Record: https://patchnext.com/advisories/cve-2026-44797 (revision 2, source checked 26 Oct 2026, 13:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nautobot 3.1.2, 2.4.33. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI nautobot: affected >= 3.0.0a2, < 3.1.2; < 2.4.33; fixed in 3.1.2, 2.4.33

## Suggested inspection (read-only)
- `python -m pip show nautobot`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nautobot.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-c35q-vxrp-ph26 (OSV record GHSA-c35q-vxrp-ph26 lists affected ranges: PyPI nautobot >=3.0.0a2 =0 <2.4.33 (fixed))
- Verified: https://github.com/advisories/GHSA-c35q-vxrp-ph26 (GitHub-reviewed advisory GHSA-c35q-vxrp-ph26 lists affected ranges: PyPI nautobot >=3.0.0a2 =0 <2.4.33)

Commands are suggestions: review each one before running it.

Loading voting…