CVE-2026-44798: Nautobot: GitRepository.current_head field should not be writable through REST API
(updated )
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.
References
- github.com/advisories/GHSA-p3hx-pwf3-j8wr
- github.com/nautobot/nautobot/commit/9deddfc91ad9260ad17b5e20084e9e2d15be3609
- github.com/nautobot/nautobot/commit/c46f97040b2bde4320be36b23577f19a8bcbd8c3
- github.com/nautobot/nautobot/releases/tag/v2.4.33
- github.com/nautobot/nautobot/releases/tag/v3.1.2
- github.com/nautobot/nautobot/security/advisories/GHSA-p3hx-pwf3-j8wr
- nvd.nist.gov/vuln/detail/CVE-2026-44798
Code Behaviors & Features
Detect and mitigate CVE-2026-44798 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →