CVE-2026-44798: Nautobot GitRepository.current_head Field Should Not Be Vulnerability

HIGH
Advisory Identifier: GHSA-p3hx-pwf3-j8wr
Share
CVSS 7.1
CWE-749 CWE-471
Published
Advisory Summary

CVE-2026-44798 is a HIGH (CVSS 7.1) gitrepository.current_head field should not be vulnerability (CWE-749: Exposed Dangerous Method or Function) affecting Nautobot libraries in the PyPI ecosystem. The issue involves gitrepository.current_head field should not be writable through rest api. Remediation is available by upgrading affected packages to version 3.1.2, 2.4.33.

CVE-2026-44798 at a Glance

CVE Identifier CVE-2026-44798
GHSA Identifier GHSA-p3hx-pwf3-j8wr
Severity HIGH
CVSS v3.1 Base Score 7.1
CWE Classification CWE-749: Exposed Dangerous Method or Function
Affected Product Nautobot
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 7.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity Low (I:L)
Availability High (A:H)

How to Fix CVE-2026-44798

To remediate this vulnerability, upgrade all affected Nautobot dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

nautobot fixed: 3.1.2 
pip install nautobot>=3.1.2
nautobot fixed: 2.4.33 
pip install nautobot>=2.4.33
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

pip show nautobot

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-44798, inspect your installed packages using pip:

pip show nautobot

Analyze the terminal output to locate any version of Nautobot in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.1.2), your application is affected.

Note: The pip show nautobot command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-749: Exposed Dangerous Method or Function, where the product provides an applications programming interface (api) or similar interface for interaction with external actors, but the interface includes a dangerous method or function that is not properly restricted. In Nautobot, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact 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. ### Patches The issue has been remediated in Nautobot v2.4.33 and 3.1.2. ### Workarounds Note that many of the same end-result symptoms could be caused by a user with the same level of access simply changing the `branch` or `remote_url` of a GitRepository rather than crafting the `current_head`. Administrators are encouraged to carefully review which users are granted permissions to create and modify GitRepository records. ### References - 2.4.33 (<a href="https://github.com/nautobot/nautobot/commit/9deddfc91ad9260ad17b5e20084e9e2d15be3609">patch</a>) - 3.1.2 (<a href="https://github.com/nautobot/nautobot/commit/c46f97040b2bde4320be36b23577f19a8bcbd8c3">patch</a>)

CVE-2026-44798 Affected Nautobot Versions

2 component(s)
Fixed Versions:
3.1.22.4.33
Product / Package Ecosystem Affected Versions Fixed Version
nautobot
pypi/nautobot
PyPI
≥ 3.0.0a2
< 3.1.2
3.1.2
nautobot
pypi/nautobot
PyPI
< 2.4.33
2.4.33

References

GitHub Advisory / Wiki ADVISORY
https://github.com/nautobot/nautobot/security/advisories/GHSA-p3hx-pwf3-j8wr
NVD — CVE-2026-44798 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-44798
Security Fix Commit FIX COMMIT
https://github.com/nautobot/nautobot/commit/9deddfc91ad9260ad17b5e20084e9e2d15be3609
Security Fix Commit FIX COMMIT
https://github.com/nautobot/nautobot/commit/c46f97040b2bde4320be36b23577f19a8bcbd8c3
Nautobot Source Repository REPOSITORY
https://github.com/nautobot/nautobot
Nautobot Release RELEASE
https://github.com/nautobot/nautobot/releases/tag/v2.4.33
Nautobot Release RELEASE
https://github.com/nautobot/nautobot/releases/tag/v3.1.2

Frequently Asked Questions

What is CVE-2026-44798?
CVE-2026-44798 is a security vulnerability in Nautobot involving GitRepository.current_head field should not be writable through REST API under CWE-749: Exposed Dangerous Method or Function.
Which Nautobot versions are affected?
Affected versions include releases prior to 3.1.2, 2.4.33 across affected packages: nautobot.
What version fixes CVE-2026-44798?
Upgrading to 3.1.2, 2.4.33 (or the latest patched release for your respective branch) resolves the vulnerability.
Is nautobot affected?
Yes, nautobot is affected in releases prior to 3.1.2, 2.4.33. Upgrade your dependency to 3.1.2, 2.4.33 or later.
What is the CVSS score of CVE-2026-44798?
CVE-2026-44798 has a CVSS v3.1 base score of 7.1 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H.
What CWE is associated with CVE-2026-44798?
CVE-2026-44798 is classified under CWE-749: Exposed Dangerous Method or Function (The product provides an Applications Programming Interface (API) or similar interface for interaction with external actors, but the interface includes a dangerous method or function that is not properly restricted.).
How can I check PyPI dependencies for CVE-2026-44798?
Run the dependency tree command: 'pip show nautobot'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-p3hx-pwf3-j8wr",
  "modified" : "2026-06-09T10:18:49Z",
  "published" : "2026-05-13T15:31:04Z",
  "aliases" : [ "CVE-2026-44798" ],
  "summary" : "Nautobot: GitRepository.current_head field should not be writable through REST API",
  "details" : "### Impact\n\nA 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.\n\n### Patches\n\nThe issue has been remediated in Nautobot v2.4.33 and 3.1.2.\n\n\n### Workarounds\n\nNote that many of the same end-result symptoms could be caused by a user with the same level of access simply changing the `branch` or `remote_url` of a GitRepository rather than crafting the `current_head`. Administrators are encouraged to carefully review which users are granted permissions to create and modify GitRepository records.\n\n\n### References\n\n- 2.4.33 (<a href=\"https://github.com/nautobot/nautobot/commit/9deddfc91ad9260ad17b5e20084e9e2d15be3609\">patch</a>)\n- 3.1.2 (<a href=\"https://github.com/nautobot/nautobot/commit/c46f97040b2bde4320be36b23577f19a8bcbd8c3\">patch</a>)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "nautobot"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.0.0a2"
      }, {
        "fixed" : "3.1.2"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "nautobot"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.4.33"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/nautobot/nautobot/security/advisories/GHSA-p3hx-pwf3-j8wr"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-44798"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nautobot/nautobot/commit/9deddfc91ad9260ad17b5e20084e9e2d15be3609"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nautobot/nautobot/commit/c46f97040b2bde4320be36b23577f19a8bcbd8c3"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/nautobot/nautobot"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nautobot/nautobot/releases/tag/v2.4.33"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nautobot/nautobot/releases/tag/v3.1.2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-471", "CWE-749" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-13T15:31:04Z",
    "nvd_published_at" : "2026-05-28T18:16:34Z"
  }
}