Fleet MDM CVE-2026-54245

Requires Fleet Premium with the Okta conditional access integration explicitly configured and enabled - instances without this feature are unaffected. The attacker must control at least one host already enrolled in the Fleet instance; this is the minimum foothold required, corresponding to the product's lowest-privilege role. The vulnerable request path itself is unauthenticated (the host agent communicates without user-level authentication), but the precondition of having an enrolled host limits exploitation to parties who have already compromised at least one managed endpoint. Exploitation is not limited to a specific operating system for the attacker's host. What limits scope: the Okta conditional access feature must be active (non-default for most deployments), and initial host enrollment must already be achieved - cold external attackers with no enrolled host cannot trigger the injection.

The CVSS 4.0 vector (AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N) accurately captures the primary risk profile: network-reachable, no user interaction required, but gated behind a specific attack prerequisite (AT:P) - Fleet Premium with Okta conditional access enabled. PR:L reflects that the attacker must control at least one enrolled host, which is the product's lowest-privilege entry point. The confidentiality (VC:H) and integrity (VI:H) impacts are high because the Fleet database stores session tokens for all users including administrators. The vendor's vector scores SC/SI/SA as N, but this understates the lateral impact: successfully replaying a global admin session token enables execution of scripts across all enrolled hosts, representing a substantial subsequent-system impact. Real-world priority is high for any Fleet Premium deployment with Okta conditional access, and low for all others - this is not a spray-and-pray vulnerability. No CISA KEV listing and no public POC have been identified, reducing the urgency slightly for organizations that can verify the feature is disabled.

An attacker with control of a single enrolled host - gained, for example, through malware infection, physical access, or a compromised developer machine - manipulates the values that the host's osquery agent reports to the Fleet server. When Fleet's Okta conditional access endpoint processes these values in an unsanitized database query, the attacker extracts session tokens for all Fleet users including global administrators. The attacker then replays a global admin token via the Fleet API and uses the administrative script-execution feature to run arbitrary commands on every other host enrolled in the Fleet instance.