CVE-2026-23999
MEDIUMDescription
Fleet is open source device management software. In versions prior to 4.80.1, 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, and 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. Version 4.80.1 contains a patch. No known workarounds are available.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 2% of all known CVEs.
References
Related Vulnerabilities
Other CWE-330 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2019-5420 | Critical | 9.8 | 92% | - | Fix |
| CVE-2021-34646 | Critical | 9.8 | 51% | - | - |
| CVE-2008-0087 | High | 7.5 | 32% | - | - |
| CVE-2017-6026 | Critical | 9.1 | 32% | - | - |
| CVE-2018-17888 | Critical | 9.8 | 30% | - | - |
| CVE-2020-11901 | Critical | 9.0 | 21% | - | Fix |
Common questions
How do I fix CVE-2026-23999?
Upgrade fleet to 4.80.1 or later.
Is CVE-2026-23999 being actively exploited?
Not that we know of. CVE-2026-23999 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.12% is the estimated probability that it will be exploited in the next 30 days. That is higher than 2% of all scored CVEs.
How severe is CVE-2026-23999?
CVE-2026-23999 has a CVSS v3 base score of 5.5, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-23999 affect?
Published advisories record a fix for fleet (NVD). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-23999
Markdown
[](https://tridentstack.com/cve/CVE-2026-23999)HTML
<a href="https://tridentstack.com/cve/CVE-2026-23999"><img src="https://tridentstack.com/cve/badge/CVE-2026-23999.svg" alt="CVE-2026-23999"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-03-02.