Skip to content
Fencer Intel
high 7.1

CVE-2026-44798 json

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

published 5mo ago modified 26d ago also GHSA-p3hx-pwf3-j8wr , PYSEC-2026-2228 , EUVD-2026-32973

cvss
7.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 20%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi nautobot 2.4.33, 3.1.2
  • networktocode nautobot 2.4.33, 3.1.2

Is CVE-2026-44798 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
5mo ago

Exploit prediction

0.28% chance of exploitation in the next 30 days, higher than 20% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H
OSV 3.1 7.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H
GitHub 3.1 7.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H

Affected packages

ecosystem package affected fixed in
pypi nautobot
>=3.0.0a2, <3.1.2
<2.4.33
>=3.0.0, <3.1.2
3.1.2
2.4.33

Affected products

  • nautobot nautobot

Classification

Weakness
  • CWE-471 Modification of Assumed-Immutable Data (MAID)
  • CWE-749 Exposed Dangerous Method or Function

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.