CVE-2026-23999: 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.
Published Feb 26, 2026 · Updated Mar 10, 2026
Affected packages
github.com/fleetdm/fleet/v4
- Ecosystem
- Go
- Affected
- < 4.80.1
- Fixed in
- 4.80.1
- Check
go list -m github.com/fleetdm/fleet/v4
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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:
- Physical access to the device is required.
- The approximate lock time must be known.
- The operating system enforces rate limiting on PIN entry attempts.
- Attempts would need to be spread over multiple days.
- Device wipe operations would typically complete before sufficient attempts could be made.
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.
Credited to prateek-0490.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesGHSA-q9c5-pp7m-fm2g
Fleet: Unauthenticated download of in-house iOS app binaries via predictable URLs
medium5.3Aug 20, 2026GHSA-rxhg-vcww-2mpw
Fleet: ORDER BY column injection on activity list endpoints
low3.1Aug 20, 2026CVE-2026-48786
Fleet: Observer-class users can view team enroll secrets and credential-bearing configuration via target search endpoint
medium6.5Aug 12, 2026CVE-2026-41262
Fleet DM Vulnerable to Cross-Team Policy Data Exposure via Global Policy Read Endpoint
medium4.3Jun 26, 2026CVE-2026-46370
Fleet has observer-level enrollment secret extraction via ORDER BY oracle on labels host-listing endpoint
medium6.5Jun 12, 2026CVE-2026-46371
Fleet: Observer-level enrollment secret extraction via ORDER BY oracle on Apple MDM commands endpoint
medium6.5Jun 12, 2026
