Log in Start free

Vulnerability · Published May 28, 2026 · Assigned by GitHub_M

CVE-2026-44798Nautobot: GitRepository.current_head field should not be writable through REST API

High 7.1

In plain English

A high-severity security flaw in nautobot from nautobot. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 20% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.1High
Exploit odds (30 days)0.3%top 79.8% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

Nautobot is a Network Source of Truth and Network Automation Platform. Prior to 2.4.33 and 3.1.2, a user with access to add/change a GitRepository record could use the REST API to directly set the current_head field on the record, which was not intended to be user-editable. Doing so could cause Nautobot's local clone(s) of the relevant repository to checkout a commit other than the latest commit on the specified branch (resulting in misleading state), or potentially to be unable to make use of the repository at all (until manually remediated) due to the current_head pointing to a nonexistent commit hash or malformed value. This vulnerability is fixed in 2.4.33 and 3.1.2.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
PyPInautobot3.1.2GHSA-p3hx-pwf3-j8wr
PyPInautobot2.4.33GHSA-p3hx-pwf3-j8wr
PyPInautobot2.4.33, 3.1.2PYSEC-2026-2228

Affected products (as reported)

VendorProductVersions
nautobot nautobot >= 3.0.0a2, < 3.1.2< 2.4.33

Weakness: CWE-471, CWE-749 · Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H

References