Security readout for executives and security teams
Plain-English summary
Fleet versions before 4.80.1 generated device lock and wipe PINs predictably from the current Unix timestamp. If someone has the locked device and knows roughly when the lock command was issued, they may be able to guess the 6-digit PIN. This is a low-urgency issue because it requires physical access and timing knowledge, and operating systems rate-limit attempts.
Executive priority
Low priority, but easy to justify in routine patching. The issue is narrow and physically constrained, but upgrading removes a weakness in lost-device response. Organizations that frequently lock or wipe devices through Fleet should schedule the update promptly.
Technical view
CVE-2026-23999 is a CWE-330 predictable value issue in Fleet device lock and wipe PIN generation before 4.80.1. PINs were deterministically derived from the current timestamp without a secret key or additional entropy. The CVSS v4.0 score is 0.6, with physical attack vector and high confidentiality impact only in constrained circumstances.
Likely exposure
Organizations using Fleet before 4.80.1 and relying on Fleet device lock or wipe workflows are potentially exposed. Exposure is limited to scenarios where an attacker physically possesses a locked device and can estimate the lock time. Sources do not indicate remote exploitation, fleet-wide compromise, or Fleet authentication bypass.
Exploitation context
The advisory describes exploitation as theoretical and constrained. The attacker needs physical device access and approximate lock timing. OS PIN-entry rate limiting and wipe completion timelines reduce practicality. The CVE record marks exploit maturity as unreported, and the source bundle does not identify active exploitation or CISA KEV listing.
Researcher notes
Evidence is limited to the CVE record and Fleet GitHub advisory. No workaround is listed, and the only named fix is version 4.80.1. Do not assume broader MDM impact beyond Fleet. The described weakness is predictable generation of 6-digit lock and wipe PINs from timestamp alone.
Mitigation direction
- Upgrade Fleet to version 4.80.1 or later.
- Prioritize devices and environments using Fleet lock or wipe commands.
- If upgrade timing is uncertain, check Fleet’s advisory for current guidance.
- Treat physically lost devices as potentially exposed until Fleet is updated.
Validation and detection
- Inventory Fleet server versions and confirm whether any are below 4.80.1.
- Review device management workflows for lock and wipe command usage.
- Confirm Fleet is updated to 4.80.1 or later after remediation.
- Check the Fleet advisory and CVE record for any updated guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-330: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-23999 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 0.6 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:P/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:U
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:P/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:U——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
0.6LowVector: CVSS:4.0/AV:P/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:U
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/fleetdm/fleet/security/advisories/GHSA-ppwx-5jq7-px2wCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of Insufficiently Random Values
Use of Insufficiently Random Values represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.