MediumGHSA-4f9r-x588-pp2hCVE-2026-34389GO-2026-4912

Fleet's user account creation via invite does not enforce invited email address

Published 30 Mar 2026 · Updated 2 Apr 2026

Is your project on an affected github.com/fleetdm/fleet/v4?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<4.81.0
Fixed in
4.81.0
Update to the fixed version for your release line, for example:go get github.com/fleetdm/fleet/v4@v4.81.0

Details

Summary

Fleet contained an issue in the user invitation flow where the email address provided during invite acceptance was not validated against the email address associated with the invite. An attacker who obtained a valid invite token could create an account under an arbitrary email address while inheriting the role granted by the invite, including global admin.

Impact

If an attacker gains access to a valid invite token, they can create a Fleet user account with an email address of their choosing while inheriting the invite’s assigned role and team memberships.

This issue:

  • Requires possession of a valid invite token
  • Does not bypass authentication controls beyond invite-based account creation
  • Does not expose data without successful account creation

Workarounds

If upgrading immediately is not possible:

  • Treat invite links as sensitive credentials and avoid sharing them in public or semi-public channels (e.g., Slack, Teams).
  • Revoke and reissue invites if there is any concern that an invite link may have been exposed.
  • Prefer issuing invites with the minimum required privileges and elevating roles after account creation when appropriate.

For more information

If there are any questions or comments about this advisory:

Send an email to [security@fleetdm.com](mailto:security@fleetdm.com)

Credits

Fleet thanks @fuzzztf for responsibly reporting this issue.

Is GHSA-4f9r-x588-pp2h in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/fleetdm/fleet/v4, and gives you the command that fixes it.

More advisories for github.com/fleetdm/fleet/v4

  • LowCVE-2026-54245Fleet: SQL injection in Okta conditional access endpoint allows host-controlled compromise of the Fleet database in github.com/fleetdm/fleet · 25 Aug 2026
  • LowCVE-2026-101047Fleet: Unauthenticated download of in-house iOS app binaries via predictable URLs in github.com/fleetdm/fleet · 25 Aug 2026
  • LowCVE-2026-101046Fleet: ORDER BY column injection on activity list endpoints in github.com/fleetdm/fleet · 25 Aug 2026
  • LowCVE-2026-101046Fleet: ORDER BY column injection on activity list endpoints · 20 Aug 2026
  • MediumCVE-2026-101047Fleet: Unauthenticated download of in-house iOS app binaries via predictable URLs · 20 Aug 2026
  • LowCVE-2026-48786Fleet: Observer-class users can view team enroll secrets and credential-bearing configuration via target search endpoint in github.com/fleetdm/fleet · 18 Aug 2026
All 59 advisories for github.com/fleetdm/fleet/v4

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.