Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

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

LowCVSS 0.6 · v4.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 2/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.14% (FIRST EPSS).
  • Physical access to the device is required. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: github.com/fleetdm/fleet/v4 (Go) 4.80.1; govulncheck-vulndb (openSUSE:Leap 15.6) 0.0.20260317T205859-150000.1.152.1.

Low priority for now. Upgrade to github.com/fleetdm/fleet/v4 (Go) 4.80.1; govulncheck-vulndb (openSUSE:Leap 15.6) 0.0.20260317T205859-150000.1.152.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Feb 25, 2026
Updated
Jun 17, 2026
EPSS
0.1% · 3th percentile

Report tools

JSON

Action score

2

Monitor

Low priority for now.

CVSS
2 / 40 · 0.6 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
0.6
NVD has not scored this yet; the score shown is the CNA’s.

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-23999

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
fleetdmfleet

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • fleetdm fleet

    • < 4.80.1affected

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • fleetdm fleetbefore 4.80.1

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gogithub.com/fleetdm/fleet/v4before 4.80.14.80.1
openSUSE:Leap 15.6govulncheck-vulndbbefore 0.0.20260317T205859-150000.1.152.10.0.20260317T205859-150000.1.152.1

Other highest-scoring records for the same primary product.

  • CVE-2020-26276SAML authentication vulnerability in Fleet
    40Plan
  • CVE-2026-103264Fleet before 4.87.0 Authentication Bypass via Device Identifiers
    37Monitor
  • CVE-2026-23518Fleet has a JWT signature bypass vulnerability in Azure AD MDM enrollment
    37Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2026-23517Jan 21, 2026 · Fleet has an Access Control vulnerability in debug/pprof endpoints
    25Monitor
  • ← EarlierCVE-2026-26186Feb 25, 2026 · Fleet has a SQL injection via backtick escape in ORDER BY parameter
    20Monitor
  • Later →CVE-2026-24004Feb 25, 2026 · Fleet: Unauthenticated Android device disenrollment vulnerability via Pub/Sub endpoint
    6Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Go:github.com/fleetdm/fleet/v44.80.1Package registry (OSV)
opensuse:govulncheck-vulndb0.0.20260317T205859-150000.1.152.1 · openSUSE:Leap 15.6Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Physical access to the device is required.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Physical
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
X

CVSS 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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records