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.

Project Subscriptions

Vendors Products
Nautobot Subscribe
Nautobot Subscribe
Networktocode Subscribe
Nautobot Subscribe
Advisories
Source ID Title
Github GHSA Github GHSA GHSA-p3hx-pwf3-j8wr Nautobot: GitRepository.current_head field should not be writable through REST API
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

Thu, 28 May 2026 20:15:00 +0000

Type Values Removed Values Added
First Time appeared Nautobot
Nautobot nautobot
Vendors & Products Nautobot
Nautobot nautobot

Thu, 28 May 2026 19:45:00 +0000

Type Values Removed Values Added
First Time appeared Networktocode
Networktocode nautobot
CPEs cpe:2.3:a:networktocode:nautobot:*:*:*:*:*:*:*:*
Vendors & Products Networktocode
Networktocode nautobot

Thu, 28 May 2026 19:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Thu, 28 May 2026 18:00:00 +0000

Type Values Removed Values Added
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.
Title Nautobot: GitRepository.current_head field should not be writable through REST API
Weaknesses CWE-471
CWE-749
References
Metrics cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H'}


Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-05-28T19:02:15.222Z

Reserved: 2026-05-07T19:20:44.693Z

Link: CVE-2026-44798

cve-icon Vulnrichment

Updated: 2026-05-28T19:01:58.961Z

cve-icon NVD

Status : Analyzed

Published: 2026-05-28T18:16:34.007

Modified: 2026-05-28T19:30:57.857

Link: CVE-2026-44798

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-05-28T20:00:14Z

Weaknesses