Is CVE-2026-44798 exploited in the wild?

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

How severe is CVE-2026-44798?

High severity, with a CVSS score of 7.1, 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-44798?

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-44798 attacked?

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

Am I affected by CVE-2026-44798?

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-44798: Nautobot unauthorized data modification in GitRepository API

CVE-2026-44798 · Severity: high · CVSS 7.1 · Published 2026-05-28

Nautobot is a platform used for managing network infrastructure and automation. A vulnerability in its API allows users with basic permissions to modify internal data fields that should be read-only. An attacker could use this to force the system to use incorrect or malicious versions of configuration files, potentially leading to a loss of control over network automation or a complete service outage.

Technologies: nautobot (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-44798 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-44798 being exploited in the wild.
How severe is CVE-2026-44798?: High severity, with a CVSS score of 7.1, 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-44798?: 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-44798 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-44798?: 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 vulnerability classified as CWE-471 (Modification of Assumed-Immutable Data) exists in Nautobot's REST API. The 'current_head' field of a GitRepository record, which is intended to be internal and read-only, is incorrectly writable. An authenticated attacker with permissions to add or change GitRepository records can use the API to manually set this field to an arbitrary commit hash or malformed value. This can force Nautobot to check out an incorrect commit, leading to a misleading operational state, or cause the repository integration to fail entirely. The issue is fixed in versions 2.4.33 and 3.1.2.

Affected products

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

Identifiers

CVE-2026-44798
GHSA-p3hx-pwf3-j8wr
PYSEC-2026-2228

Timeline

2026-05-08: disclosed: Initial disclosure by reporter
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.