dbcve.org
FleetApplication · Fleetdm

CVE-2026-29180

HIGH · 8.8 CVSS v3.1 Published 2026-03-27
Fix available
A fix is available. Upgrade to 4.81.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Fleet is open source device management software. Prior to 4.81.1, 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. Version 4.81.1 patches the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A broken access control vulnerability in Fleet's host transfer API prior to version 4.81.1 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.

MitigationUpgrade to Fleet version 4.81.1 or later which patches the broken access control vulnerability in the host transfer API.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FleetApplication
Affected:< 4.81.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Fleet server version
    Run 'fleetctl version' or check the Fleet UI footer/version page to identify the installed Fleet version
    Affected if Version is below 4.81.1
  2. Verify team maintainer accounts exist
    Query Fleet for users with the 'maintainer' role within any team using 'fleetctl get teams' or the API endpoint /api/v1/fleet/teams to list team membership and roles
    Affected if There are team maintainer users configured in the environment
  3. Inspect host transfer API configuration
    Review Fleet's API settings and logs for the /api/v1/fleet/hosts/transfer endpoint to determine if the host transfer feature is accessible to team maintainers
    Affected if Team maintainers have API access to transfer hosts between teams
  4. Review recent host transfer activity
    Check Fleet audit logs or host history for transfers where hosts moved from one team to another, especially transfers initiated by team maintainer accounts
    Affected if Host transfers occurred from teams the maintainer was not originally a member of

The environment is affected if Fleet version is below 4.81.1 AND team maintainers have access to the host transfer API, enabling unauthorized host transfers between teams.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.81.1 or later
Fixed in 4.81.1
Interim mitigation

Upgrade to Fleet version 4.81.1 or later which patches the broken access control vulnerability in the host transfer API.

Recommended fix High confidence

Fleet 4.81.1

  1. Identify current Fleet version using `fleetctl version` or the Fleet UI
  2. Upgrade Fleet to version 4.81.1 by following the standard upgrade process for your deployment method (e.g., `fleetctl update`, Helm chart upgrade, or Docker container update)
  3. After upgrade, verify the new version is running with `fleetctl version`
  4. Confirm the vulnerability is remediated by testing that team maintainers can no longer transfer hosts from teams they do not administer

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fleet Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-29180 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-29180 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data