# CVE-2026-34389: Fleet's user account creation via invite does not enforce invited email address

> Attackers with a valid invite token can create accounts with arbitrary emails while inheriting high-privilege roles like global admin.


- **Severity:** Medium 4.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Mar 2026
- **Updated:** 30 Mar 2026
- **Also known as:** GHSA-4f9r-x588-pp2h, GO-2026-4912

## What is CVE-2026-34389?

CVE-2026-34389 is a medium-severity authentication bypass vulnerability in fleetdm fleet, published on 27 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-34389?

3 open source packages ship an affected version, including github.com/fleetdm/fleet/v4. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/fleetdm/fleet/v4` | Go | All versions | 4.81.0 |
| `github.com/fleetdm/fleet/v4` | Go | All versions | 4.81.0 |
| `github.com/fleetdm/fleet/v4` | Go | All versions | 4.81.0 |

Products: Fleetdm Fleet.

## How do I fix CVE-2026-34389?

Upgrade github.com/fleetdm/fleet/v4 to 4.81.0 or later.

## Is CVE-2026-34389 being exploited?

There is no known exploitation of CVE-2026-34389 in the wild and no public exploit code.

## Other vulnerabilities in fleetdm fleet

- [CVE-2020-26276](https://insights.sbomify.com/CVE-2020-26276/): SAML authentication vulnerability in Fleet (critical 10.0)
- [CVE-2026-103264](https://insights.sbomify.com/CVE-2026-103264/): Fleet before 4.87.0 Authentication Bypass via Device Identifiers (critical 9.3)
- [CVE-2026-23518](https://insights.sbomify.com/CVE-2026-23518/): Fleet has a JWT signature bypass vulnerability in Azure AD MDM enrollment (critical 9.3)
- [CVE-2026-26062](https://insights.sbomify.com/CVE-2026-26062/): Fleet server may terminate unexpectedly when handling certain gRPC requests (high 8.7)
- [CVE-2026-26061](https://insights.sbomify.com/CVE-2026-26061/): Fleet's unbounded request body read allows remote Denial of Service (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-34389 and fix it if it is affected.

What it is: CVE-2026-34389 is a medium-severity authentication bypass vulnerability in fleetdm fleet, published on 27 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-34389 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/fleetdm/fleet/v4 (Go): affected all versions; fixed in 4.81.0
- github.com/fleetdm/fleet/v4 (Go): affected all versions; fixed in 4.81.0
- github.com/fleetdm/fleet/v4 (Go): affected all versions; fixed in 4.81.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-34389/ (Markdown: https://insights.sbomify.com/CVE-2026-34389/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-34389
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-34389
- OSV: https://osv.dev/vulnerability/CVE-2026-34389

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-34389/
Summaries are generated and may contain mistakes; the official description above is the record.