Is CVE-2026-44797 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-44797 being exploited in the wild.

How severe is CVE-2026-44797?

High severity, with a CVSS score of 8.5, published 28 May 2026.

Which products and versions are affected?

nautobot (PyPI) ECOSYSTEM:introduced=0,fixed=2.4.33,introduced=3.0.0,fixed=3.1.2, ECOSYSTEM:introduced=3.0.0a2,fixed=3.1.2.

Is there a fix for CVE-2026-44797?

Yes. nautobot (PyPI): upgrade to 3.1.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-44797 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-44797?

Check whether you run nautobot (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-44797: Nautobot SSRF in Webhook data model

CVE-2026-44797 · Severity: high · CVSS 8.5 · Published 2026-05-28

Nautobot is a platform used for managing network infrastructure and automation. A vulnerability in its webhook system allows users with certain permissions to force the server to send requests to unauthorized internal or external locations. This could be used to bypass network security controls, access sensitive internal data, or disrupt operations.

Technologies: nautobot (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-44797 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-44797 being exploited in the wild.
How severe is CVE-2026-44797?: High severity, with a CVSS score of 8.5, published 28 May 2026.
Which products and versions are affected?: nautobot (PyPI) ECOSYSTEM:introduced=0,fixed=2.4.33,introduced=3.0.0,fixed=3.1.2, ECOSYSTEM:introduced=3.0.0a2,fixed=3.1.2.
Is there a fix for CVE-2026-44797?: Yes. nautobot (PyPI): upgrade to 3.1.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-44797 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-44797?: Check whether you run nautobot (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

nautobot (PyPI): upgrade to 3.1.2 or later
```
pip install "nautobot>=3.1.2"
```

Technical details

A Server-Side Request Forgery (SSRF) vulnerability exists in Nautobot's Webhook data model (CWE-918). Users with 'add' or 'change' permissions for webhooks can configure the system to perform requests to arbitrary hosts, IP addresses, or URI schemes that should be restricted. This occurs because the application does not sufficiently validate the destination of webhook requests. Attackers can leverage this to probe internal networks or access metadata services. Patches in v2.4.33 and v3.1.2 introduce new configuration variables (WEBHOOK_ALLOWED_SCHEMES, WEBHOOK_ADDITIONAL_BLOCKED_NETWORKS, and WEBHOOK_ALLOWED_HOSTS) to enforce strict allow-lists and block-lists for webhook destinations.

Affected products

Nautobot Nautobot < 2.4.33, >= 3.0.0a2, < 3.1.2

Identifiers

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

Timeline

2026-05-08: disclosed
2026-05-13: advisory: GitHub Advisory published
2026-05-28: other: NVD published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.