CVE-2026-44798 Nautobot: GitRepository.current_head field should not be writable through REST API
Attackers with repository access can manipulate Git HEAD pointers via API, causing misleading states or service disruption in Nautobot.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-44798?
CVE-2026-44798 is a high-severity missing authorization vulnerability in nautobot, published on 28 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
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.
Which versions are affected by CVE-2026-44798?
5 open source packages ship an affected version, including nautobot. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
nautobot PyPI | All versions | 2.4.33, 3.1.2 |
nautobot PyPI | All versions | 2.4.33 |
nautobot PyPI | All versions | 2.4.33 |
nautobot PyPI | From 3.0.0a2 | 3.1.2 |
nautobot PyPI | From 3.0.0a2 | 3.1.2 |
Products include Networktocode Nautobot.
How do I fix CVE-2026-44798?
Upgrade nautobot to a fixed version for your release line: 2.4.33 or 3.1.2.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-44798 being exploited?
There is no known exploitation of CVE-2026-44798 in the wild and no public exploit code.
Other vulnerabilities in nautobot
- CVE-2026-44797 Nautobot: Webhook definitions could be used for server-side request forgery (SSRF)
- CVE-2024-34707 Nautobot's BANNER_* configuration can be used to inject arbitrary HTML content into Nautobot pages
- CVE-2024-32979 Reflected Cross-site Scripting potential in all object list views in Nautobot
- CVE-2023-25657 Remote code execution in Jinja2 template rendering in Nautobot
- CVE-2024-23345 Nautobot has XSS potential in rendered Markdown fields
Sources
Also known as GHSA-p3hx-pwf3-j8wr, PYSEC-2026-2228.