cve.bz

CVE-2026-44798 networktocode nautobot: Exposed Dangerous Method or Function

7.1 highEPSS 0.3%Fix available

High (7.1) in networktocode nautobot. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in nautobot 2.4.33, 3.1.2.

On this page
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.

Severity

CVSS 3.1

7.1 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 20th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-05-28. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-471 Modification of Assumed-Immutable Data (MAID)
CWE-749 Exposed Dangerous Method or Function
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-44798 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-44798?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-44798?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-44798 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
networktocode:nautobotbefore 2.4.33
networktocode:nautobotfrom 3.0.0 before 3.1.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-p3hx-pwf3-j8wrPyPInautobot>=3.0.0a2 <3.1.23.1.2
GHSA-p3hx-pwf3-j8wrPyPInautobot<2.4.332.4.33
PYSEC-2026-2228PyPInautobot<2.4.33
>=3.0.0 <3.1.2
2.4.33, 3.1.2

Attack patterns (CAPEC)

  • CAPEC-500 WebView Injection
  • CAPEC-384 Application API Message Manipulation via Man-in-the-Middle Severity: Low
  • CAPEC-385 Transaction or Event Tampering via Application API Manipulation Severity: Medium
  • CAPEC-386 Application API Navigation Remapping Severity: Medium
  • CAPEC-387 Navigation Remapping To Propagate Malicious Content Severity: Medium
  • CAPEC-388 Application API Button Hijacking Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON