github.com/fleetdm/fleet/v4
Affected
- introduced
0, fixed4.80.1(semver)
Fixed versions
4.80.1
Fix
- Fixed version
4.80.1go get github.com/fleetdm/fleet/[email protected]
Advisory
Also known as: CVE-2026-23999, GO-2026-4564
Fleet: Device lock PIN can be predicted if lock time is known
Summary
Fleet generated device lock and wipe PINs using a predictable algorithm based solely on the current Unix timestamp. Because no secret key or additional entropy was used, the resulting PIN could potentially be derived if the approximate time the device was locked is known.
Impact
Fleet’s device lock and wipe commands generate a 6-digit PIN that is displayed to administrators for unlocking a device. In affected versions, this PIN was deterministically derived from the current timestamp.
An attacker with physical possession of a locked device and knowledge of the approximate time the lock command was issued could theoretically predict the correct PIN within a limited search window.
However, successful exploitation is constrained by multiple factors:
As a result, this issue does not allow remote exploitation, fleet-wide compromise, or bypass of Fleet authentication controls.
Workarounds
There are no known workarounds for this issue. Customers should upgrade to a patched version.
For more information
If there are any questions or comments about this advisory:
Email Fleet at [[email protected]](mailto:[email protected])
Join #fleet in osquery Slack
Credits
Fleet thanks @secfox-ai for responsibly reporting this issue.
Medium Basis: The source's own band: MODERATE
0, fixed 4.80.1 (semver)4.80.1
4.80.1go 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