github.com/fleetdm/fleet/v4
Affected
- introduced
4.64.0, fixed4.64.2(semver)
Fixed versions
4.64.2
Fix
- Fixed version
4.64.2go get github.com/fleetdm/fleet/[email protected]
Advisory
Also known as: CVE-2025-27509, GO-2025-3505
Fleet has SAML authentication vulnerability due to improper SAML response validation
Summary
A vulnerability in Fleet’s SAML authentication handling could allow an attacker to forge authentication assertions and gain unauthorized access to Fleet. In certain configurations, this could result in the creation of new user accounts, including administrative accounts. This issue affects Fleet deployments using single sign-on (SSO).
Impact
In vulnerable versions of Fleet, an attacker could craft a specially-formed SAML response to:
This could allow unauthorized access to Fleet, including administrative access, visibility into device data, and modification of configuration.
Patches
This issue is addressed in commit fc96cc4 and is available in Fleet version 4.64.2.
The following backport versions also address this issue:
Workarounds
If an immediate upgrade is not possible, Fleet users should temporarily disable single-sign-on (SSO) and use password authentication.
Credit
Thank you @hakivvi, as well as Jeffrey Hofmann and Colby Morgan from the Robinhood Red Team for finding and reporting this vulnerability using our responsible disclosure process.
For more information
If you have any questions or comments about this advisory:
Critical Basis: The source's own band: CRITICAL
4.64.0, fixed 4.64.2 (semver)4.64.2
4.64.2go get github.com/fleetdm/fleet/[email protected]4.63.0, fixed 4.63.2 (semver)4.63.2
4.63.2go get github.com/fleetdm/fleet/[email protected]4.62.0, fixed 4.62.4 (semver)4.62.4
4.62.4go get github.com/fleetdm/fleet/[email protected]4.54.0, fixed 4.58.1 (semver)4.58.1
4.58.1go get github.com/fleetdm/fleet/[email protected]0, fixed 4.53.2 (semver)4.53.2
4.53.2go get github.com/fleetdm/fleet/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0