CVE-2026-44798: GitRepository Manipulation in Nautobot
Platform
python
Component
nautobot
Fixed in
3.1.2
CVE-2026-44798 is a security vulnerability affecting Nautobot versions up to 3.1.1. It allows a user with permissions to modify GitRepository records to directly manipulate the current_head field via the REST API. This manipulation can lead to misleading repository state or even prevent Nautobot from utilizing the repository, requiring manual remediation.
Detect this CVE in your project
Upload your requirements.txt file and we'll tell you instantly if you're affected.
Impact and Attack Scenarios
The primary impact of CVE-2026-44798 is the potential for disruption and misrepresentation of repository data within Nautobot. An attacker who can add or modify GitRepository records can maliciously set the current_head field to point to a non-existent commit hash or an invalid value. This can effectively break Nautobot's ability to track the correct state of the repository, leading to incorrect data being displayed or used in workflows. While not a direct data breach, the manipulation of repository state can have significant operational consequences, potentially impacting deployments and automation processes. The blast radius is limited to the affected Nautobot instance and its associated repositories.
Exploitation Context
CVE-2026-44798 was published on May 13, 2026. Its CVSS score is 7.1 (HIGH). There are currently no publicly known proof-of-concept exploits. The vulnerability is not listed on KEV or EPSS, suggesting a low to medium probability of exploitation. Active campaigns are not currently known.
Threat Intelligence
Exploit Status
CVSS Vector
What do these metrics mean?
- Attack Vector
- Network — remotely exploitable over the internet. No physical or local access required. Widest attack surface.
- Attack Complexity
- Low — no special conditions required. Attacker can exploit reliably without depending on rare configurations or timing.
- Privileges Required
- Low — any valid user account is sufficient. Basic authenticated access required.
- User Interaction
- None — attack is automatic and silent. Victim does nothing: no click, no file open.
- Scope
- Unchanged — impact is limited to the vulnerable component itself.
- Confidentiality
- None — no confidentiality impact. Attacker cannot read protected data.
- Integrity
- Low — attacker can modify some data with limited scope or impact.
- Availability
- High — complete crash or resource exhaustion. Full denial of service.
Affected Software
Timeline
- Published
Mitigation and Workarounds
The recommended mitigation for CVE-2026-44798 is to upgrade to Nautobot version 3.1.2 or later, which includes the fix. If an immediate upgrade is not possible, consider restricting access to the GitRepository record modification functionality to only authorized personnel. Implement strict input validation on the currenthead field within the REST API to prevent the setting of invalid or unexpected values. Regularly audit GitRepository records for any suspicious changes. After upgrade, confirm by verifying the currenthead field on several GitRepository records reflects the expected latest commit.
How to fix
No official patch available. Check for workarounds or monitor for updates.
Frequently asked questions
What is CVE-2026-44798 — GitRepository Manipulation in Nautobot?
CVE-2026-44798 is a HIGH severity vulnerability in Nautobot versions ≤3.1.1 that allows unauthorized modification of the current_head field in GitRepository records, potentially disrupting repository access or providing misleading state.
Am I affected by CVE-2026-44798 in Nautobot?
You are affected if you are running Nautobot version 3.1.1 or earlier. Check your version and upgrade as soon as possible to mitigate the risk.
How do I fix CVE-2026-44798 in Nautobot?
Upgrade to Nautobot version 3.1.2 or later. If immediate upgrade is not possible, restrict access to GitRepository modification and implement input validation.
Is CVE-2026-44798 being actively exploited?
Currently, there are no publicly known active exploitation campaigns or proof-of-concept exploits for CVE-2026-44798.
Where can I find the official Nautobot advisory for CVE-2026-44798?
Refer to the official Nautobot security advisory for detailed information and updates regarding CVE-2026-44798: [https://nautobot.io/security/advisories/](https://nautobot.io/security/advisories/)
Is your project affected?
Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.
Detect this CVE in your project
Upload your requirements.txt file and we'll tell you instantly if you're affected.
Scan your Python project now — no account
Upload your requirements.txt and get the vulnerability report instantly. No account. Uploading the file is just the start: with an account you get continuous monitoring, Slack/email alerts, multi-project and white-label reports.
Drag & drop your dependency file
composer.lock, package-lock.json, requirements.txt, Gemfile.lock, pubspec.lock, Dockerfile...