CVE-2026-44798
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.
Scoring
- Severity
- HIGH
- CVSS base score
- 7.1
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H
- EPSS probability
- 0.28%
- CWE
- CWE-471, CWE-749
- Published
- 2026-05-28
- Last modified
- 2026-05-28
Affected products
- nautobot nautobot
- nautobot nautobot
Weakness type
Related vulnerabilities
- CVE-2026-50481 — Azure Active Directory Elevation of Privilege Vulnerability
- CVE-2026-54267 — Angular Client Hydration DOM Clobbering & Response-Cache Poisoning
- CVE-2026-8492 — Translate Drupal with GTranslate - Less critical - DOM clobbering / link manipulation - SA-CONTRIB-2026-035
- CVE-2025-33136 — IBM Aspera Faspex data modification
- CVE-2024-9876 — Application is vulnerable to Privilege escalation
- CVE-2024-55551 — An issue was discovered in Exasol JDBC driver before 24.2.1 (2024-12-10). Attackers can inject...
- CVE-2024-45672 — IBM Security Verify Bridge data manipulation
- CVE-2024-51462 — IBM QRadar WinCollect Agent data manipulation