← Back to results
Vulnerability record · public intelligence
CVE-2026-34389
MEDIUM

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

Published Mar 27, 2026 · Updated Nov 3, 2026

Severity · CVSSMEDIUM · Not scored
Known exploitationNot listed
EPSS / likelihood0.19%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Nov 3, 2026

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

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

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.

Potential 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

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

FIRST-EPSSCVE-LIST-V5NVD-MODIFIED
SSVC priority
LOW
Confidence
Not available
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Security advisory ↗

Record history

Published Mar 27, 2026 · Last refreshed Nov 3, 2026