FlawAtlas
Search the atlas
CVE-2026-34389 Moderate

Fleet's user account creation via invite does not enforce invited email address in github.com/fleetdm/fleet

Fleet's user account creation via invite does not enforce invited email address in github.com/fleetdm/fleet

Exploit probability 0.2%
Published April 2, 2026
Required by Not available
Last source change April 2, 2026

02 / AFFECTED SOFTWARE

Affected packages

Unknown Unknown

308 explicit affected versions

Go github.com/fleetdm/fleet/v4
Go github.com/fleetdm/fleet/v4

03 / CONNECTIONS

Connected vulnerabilities

related OPENSUSE-SU-2026:21483-1

04 / EVIDENCE

Source records

Open Source Vulnerabilities CVE-2026-34389

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

View original source
Open Source Vulnerabilities GHSA-4f9r-x588-pp2h

### 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 [[email protected]](mailto:[email protected]) ### Credits Fleet thanks @fuzzztf for responsibly reporting this issue.

View original source
Open Source Vulnerabilities GO-2026-4912

Fleet's user account creation via invite does not enforce invited email address in github.com/fleetdm/fleet

View original source

05 / REFERENCES

Further evidence