Maintainer-level cross-team takeover via missing source authorization
Published Mar 27, 2026 · Updated Mar 27, 2026
Broken access control in Fleet before 4.81.1 allows remote authenticated users to transfer hosts across isolated teams. The host transfer endpoints check write permission only for the destination team and omit any authorization check for the hosts' source team. Team maintainer or team admin access is required; transferred hosts adopt the attacker's team MDM settings and allow root-level script execution.
Summary
What happened
Broken access control in Fleet before 4.81.1 allows remote authenticated users to transfer hosts across isolated teams. The host transfer endpoints check write permission only for the destination team and omit any authorization check for the hosts' source team. Team maintainer or team admin access is required; transferred hosts adopt the attacker's team MDM settings and allow root-level script execution.
The record
- CVE
- CVE-2026-29180
- Published
- Mar 27, 2026
- Updated
- Mar 27, 2026
- Vendor
- Fleet Device Management
- Product
- Fleet
- Classifications
- CWE-862, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 27, 2026CVE publishedPublication date reported by the CVE source.
- Mar 27, 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=< 4.81.1
What conditions does exploitation require?
What is affected?
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.
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