CVE-2026-26060: fleetdm fleet · Insufficient Session Expiration
Affects fleetdm fleetSource CVE Database V5
Not known to be exploited · CVSS 6.0 Medium : upgrade to 4.81.0 when convenient.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.81.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 27 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade fleet and fleetdm/fleet to 4.81.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| fleetdmfleet | Affected
| Fixed in
|
GitHubfleetdm/fleetpkg:github/fleetdm/fleetOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Upgrade Fleet to version 4.81.0 or later immediately to ensure the vulnerability is patched.
- Review and enhance password reset token management policies to ensure tokens are single-use and expire promptly after password changes.
- Implement monitoring and alerting for unusual password reset activities or multiple reset attempts using the same token.
- Enforce strict access controls and audit logging around password reset token issuance and usage to detect potential misuse.
- Educate users and administrators on the importance of safeguarding password reset tokens and recognizing suspicious account activities.
- Consider integrating multi-factor authentication (MFA) for account recovery processes to add an additional security layer.
- Regularly audit Fleet deployments for outdated versions and enforce patch management policies to reduce exposure to known vulnerabilities.
- If possible, invalidate all outstanding password reset tokens during emergency password changes or suspected compromise events.
Description
Fleet is open source device management software. Prior to 4.81.0, a vulnerability in Fleet’s password management logic could allow previously issued password reset tokens to remain valid after a user changes their password. As a result, a stale password reset token could be reused to reset the account password even after a defensive password change. Version 4.81.0 patches the issue.