nautobot
Affected
- introduced
3.0.0a2, fixed3.1.2(ecosystem)
Fixed versions
3.1.2
Fix
- Fixed version
3.1.2pip install --upgrade nautobot==3.1.2
Advisory
Also known as: CVE-2026-44798, PYSEC-2026-2228
Nautobot: GitRepository.current_head field should not be writable through REST API
Impact
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.
Patches
The issue has been remediated in Nautobot v2.4.33 and 3.1.2.
Workarounds
Note that many of the same end-result symptoms could be caused by a user with the same level of access simply changing the branch or remote_url of a GitRepository rather than crafting the current_head. Administrators are encouraged to carefully review which users are granted permissions to create and modify GitRepository records.
References
High Basis: The source's own band: HIGH
3.0.0a2, fixed 3.1.2 (ecosystem)3.1.2
3.1.2pip install --upgrade nautobot==3.1.20, fixed 2.4.33 (ecosystem)2.4.33
2.4.33pip install --upgrade nautobot==2.4.33Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0