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.
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.
There are no known workarounds for this issue. Customers should upgrade to a patched version.
If there are any questions or comments about this advisory:
Email Fleet at [email protected]
Join #fleet in osquery Slack
Fleet thanks @secfox-ai for responsibly reporting this issue.
| Score | Percentile |
|---|---|
| 0.02% | 5.26% |
| Base score | Version | Severity | Vector |
|---|---|---|---|
| 4.1 | 4.0 | — |
|
| Type | Value |
|---|---|
| GHSA | GHSA-ppwx-5jq7-px2w ↗ |
| CVE | CVE-2026-23999 ↗ |
| CWE id | Name |
|---|---|
| CWE-330 | Use of Insufficiently Random Values |
Vulnerable version ranges and first patched releases as published by GitHub.
| Ecosystem | Package | Vulnerable range | First patched | Vulnerable functions |
|---|---|---|---|---|
| go | github.com/fleetdm/fleet/v4 | < 4.80.1 | 4.80.1 | — |