Repository disruption via writable current_head field
Published May 28, 2026 · Updated May 28, 2026
Improper access control in Nautobot before 2.4.33 and 3.0.0a2 through 3.1.1 allows remote authenticated users to disrupt Git repositories. GitRepositorySerializer exposed all model fields without marking current_head read-only, so REST create and update requests could write this sync-managed commit value. GitRepository add or change permission is required; a crafted value can force a stale checkout or leave the local clone unusable.
Summary
What happened
Improper access control in Nautobot before 2.4.33 and 3.0.0a2 through 3.1.1 allows remote authenticated users to disrupt Git repositories. GitRepositorySerializer exposed all model fields without marking current_head read-only, so REST create and update requests could write this sync-managed commit value. GitRepository add or change permission is required; a crafted value can force a stale checkout or leave the local clone unusable.
The record
- CVE
- CVE-2026-44798
- Published
- May 28, 2026
- Updated
- May 28, 2026
- Vendor
- Network to Code
- Product
- Nautobot
- Classifications
- CWE-471, CWE-749, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 28, 2026CVE publishedPublication date reported by the CVE source.
- May 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.4.33
- Affected versionversion=>= 3.0.0a2, < 3.1.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo