CVE-2026-44798highCWE-471CWE-749

CVE-2026-44798: high-severity vulnerability in nautobot

Nautobot: GitRepository.current_head field should not be writable through REST API

Published

Follow this CVE+ Monitor nautobot+ Monitor nautobot

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

21Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackcvss 7.1epss 0.3%
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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H
Affected products
nautobot · nautobot
Related CVEs — nautobot

In the same product, most dangerous first.

CVE-2023-25657HIGHRemote code execution in Jinja2 template rendering in NautobotEPSS 1.5%CVE-2023-50263LOWNautobot allows unauthenticated db-file-storage viewsEPSS 0.7%CVE-2023-46128MEDIUMExposure of hashed user passwords via REST API in NautobotEPSS 0.7%CVE-2024-29199LOWUnauthenticated views may expose information to anonymous usersEPSS 0.6%CVE-2024-34707HIGHNautobot's BANNER_* configuration can be used to inject arbitrary HTML content into Nautobot pagesEPSS 0.6%CVE-2023-48705HIGHnautobot has XSS potential in custom links, job buttons, and computed fieldsEPSS 0.5%