Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2026-23999— Fleet: Device lock PIN can be predicted if lock time is known

Quick assessment

Affected
fleetdm fleet
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Fleet是Fleet Device Management开源的一个设备管理平台，支持多种操作系统和设备，帮助 IT 和安全团队进行设备管理、漏洞报告、MDM 等操作。 Fleet 4.80.1之前版本存在安全特征问题漏洞，该漏洞源于设备锁定和擦除PIN生成算法可预测，可能导致物理访问设备的攻击者推导出PIN。

AI Predicted 3.1 Difficulty: Hard EPSS 0.13% · P2
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-23999

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Fleet: Device lock PIN can be predicted if lock time is known
Source: CVE Program / CVE List V5
Vulnerability Description
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.
Source: CVE Program / CVE List V5
CVSS Information
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: CVE Program / CVE List V5
Vulnerability Type
使用不充分的随机数
Source: CVE Program / CVE List V5
Vulnerability Title
Fleet 安全特征问题漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Fleet是Fleet Device Management开源的一个设备管理平台，支持多种操作系统和设备，帮助 IT 和安全团队进行设备管理、漏洞报告、MDM 等操作。 Fleet 4.80.1之前版本存在安全特征问题漏洞，该漏洞源于设备锁定和擦除PIN生成算法可预测，可能导致物理访问设备的攻击者推导出PIN。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
fleetdm fleet < 4.80.1 -

II. Public POCs for CVE-2026-23999

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-23999

请登录查看更多情报信息。

Same Patch Batch · fleetdm · 2026-02-26 · 5 CVEs total

CVE-2026-26186 Fleet has a SQL injection via backtick escape in ORDER BY parameter
CVE-2026-25963 Fleet: Authorization Bypass in certificate template batch deletion for team administrators
CVE-2026-24004 Fleet: Unauthenticated Android device disenrollment vulnerability via Pub/Sub endpoint
CVE-2026-27465 Fleet: Sensitive Google Calendar credentials disclosed to low-privileged users

IV. Related Vulnerabilities

Same product: fleet
Same vendor: fleetdm
Same weakness: CWE-330

V. Comments for CVE-2026-23999

No comments yet

Leave a comment