# CVE-2026-34389: GO-2026-4912 - Fleet's user account creation via invite does not enforce invited email address in github.com/fleetdm/fleet

Source: https://junglewise.ai/threats/cve-2026-34389-fleet-s-user-account-creation-via-invite-does-not-enforce-invited  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-03-27  
License: CC BY 4.0 with a link back

CVE-2026-34389 · Severity: medium · CVSS 6.5 · Published 2026-03-27

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.

Technologies: [Fleetdm Fleet](https://junglewise.ai/threats/technologies/fleetdm-fleet), [github.com/fleetdm/fleet/v4 (Go)](https://junglewise.ai/threats/technologies/github-com-fleetdm-fleet-v4). Vendors: [Fleetdm](https://junglewise.ai/threats/vendors/fleetdm), [Go](https://junglewise.ai/threats/vendors/go).

## Quick answers

**Is CVE-2026-34389 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-34389 being exploited in the wild.

**How severe is CVE-2026-34389?** Medium severity, with a CVSS score of 6.5, published 27 March 2026.

**Which products and versions are affected?** github.com/fleetdm/fleet/v4 (Go) SEMVER:introduced=0,fixed=4.81.0.

**Is there a fix for CVE-2026-34389?** Yes. github.com/fleetdm/fleet/v4 (Go): upgrade to 4.81.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2026-34389?** Check whether you run Fleetdm Fleet or github.com/fleetdm/fleet/v4 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/fleetdm/fleet/v4 (Go): upgrade to 4.81.0 or later

  ```sh
  go get github.com/fleetdm/fleet/v4@v4.81.0
  ```


## Affected products

- Fleetdm Fleet
- github.com/fleetdm/fleet/v4 (Go) SEMVER:introduced=0,fixed=4.81.0

## Identifiers

- CVE-2026-34389
- GHSA-4f9r-x588-pp2h
- GO-2026-4912

## Related threats

- [Fleet SQL injection in Okta conditional access endpoint](https://junglewise.ai/threats/cve-2026-54245-fleet-sql-injection-in-okta-conditional-access-endpoint)
- [Fleet SQL injection in Apple MDM commands endpoint](https://junglewise.ai/threats/cve-2026-46371-fleet-sql-injection-in-apple-mdm-commands-endpoint)
- [Fleet SQL injection in labels host-listing endpoint](https://junglewise.ai/threats/cve-2026-46370-fleet-sql-injection-in-labels-host-listing-endpoint)
- [Fleet information disclosure in target search endpoint](https://junglewise.ai/threats/cve-2026-48786-fleet-information-disclosure-in-target-search-endpoint)
- [Fleet DM cross-team policy data exposure in global policy endpoint](https://junglewise.ai/threats/cve-2026-41262-fleet-dm-cross-team-policy-data-exposure-in-global-policy)