Advisory

GHSA-m2h6-4xpq-qw3m

Also known as: CVE-2026-29180, GO-2026-4892

Summary

A Fleet team maintainer can transfer hosts from any team via missing source team authorization

Details

Summary

A broken access control vulnerability in Fleet's host transfer API allows a team maintainer to transfer hosts from any team into their own team, bypassing team isolation boundaries. Once transferred, the attacker gains full control over the stolen hosts, including the ability to execute scripts with root privileges.

Impact

The host transfer endpoints verify that the caller has write permission to the destination team but do not check whether the caller has any permission over the source team of the hosts being transferred.

Once hosts are transferred, the attacker's team MDM configuration is automatically applied to the stolen devices, and the attacker can execute scripts on them with root privileges. In multi-tenant Fleet deployments where teams represent business units, departments, or customers, this breaks all team isolation guarantees. A bulk transfer variant allows stealing all matching hosts fleet-wide in a single request.

Exploitation requires authentication as a team maintainer or team admin.

Workarounds

There is no workaround for this issue short of upgrading to a patched version. Organizations concerned about exploitation should audit host transfer activity in their Fleet logs for any unexpected team reassignments.

For more information

If there are any questions or comments about this advisory:

Email Fleet at [[email protected]](mailto:[email protected])
Join #fleet in osquery Slack

Credits

Fleet thanks @secfox-ai for responsibly reporting this issue.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-03-27 20:24 UTC
Modified
2026-04-02 21:26 UTC

Affected packages and fixes

github.com/fleetdm/fleet/v4

Go · All systems

Affected

  • introduced 0, fixed 4.81.1 (semver)

Fixed versions

4.81.1

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences