CVE-2026-26060
Received Received - Intake
Persistent Password Reset Token Vulnerability in Fleet Device Management

Publication date: 2026-03-27

Last updated on: 2026-03-31

Assigner: GitHub, Inc.

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-27
Last Modified
2026-03-31
Generated
2026-05-07
AI Q&A
2026-03-27
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
fleetdm fleet to 4.81.0 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-613 According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization."
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2026-26060 is a moderate severity vulnerability in Fleet's password management system affecting versions prior to 4.81.0.

The issue allows previously issued password reset tokens to remain valid for 24 hours even after a user changes their password.

This means that an attacker who has obtained a valid password reset token before the password change can reuse that token within its 24-hour validity window to reset the account password again.

Exploitation requires prior compromise of a reset token; the vulnerability does not enable discovery of tokens, bypass authentication independently, or affect accounts without an active reset token.

The flaw was fixed in version 4.81.0 and later.


How can this vulnerability impact me? :

This vulnerability can lead to a temporary account takeover if an attacker has previously obtained a valid password reset token.

Because the reset token remains valid for 24 hours after a password change, the attacker can reuse it to reset the account password again, potentially gaining unauthorized access.

However, exploitation requires that the attacker already has access to a valid reset token; the vulnerability does not allow token discovery or bypassing authentication on its own.

Users suspecting token exposure should wait for token expiration or contact administrators to invalidate active sessions until the issue is patched.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability involves previously issued password reset tokens remaining valid for 24 hours after a password change in Fleet versions prior to 4.81.0.

Detection would require monitoring for reuse of password reset tokens within their 24-hour validity window after a password change.

Since the vulnerability requires prior compromise of a reset token and does not enable token discovery or bypass authentication, there are no specific commands provided to detect this vulnerability directly on the network or system.


What immediate steps should I take to mitigate this vulnerability?

Upgrade Fleet to version 4.81.0 or later, where this vulnerability has been fixed.

Until the upgrade is applied, users who suspect that their password reset tokens have been exposed should wait for the tokens to expire after 24 hours.

Administrators should consider invalidating active sessions to reduce the risk of account takeover.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability in Fleet's password management system allows previously issued password reset tokens to remain valid for 24 hours after a password change, potentially enabling temporary account takeover if an attacker has obtained a reset token.

This security flaw could impact compliance with common standards and regulations such as GDPR and HIPAA, which require robust access controls and protection of user credentials to prevent unauthorized access to personal or sensitive data.

Specifically, the risk of unauthorized account access due to token reuse may violate requirements for ensuring the confidentiality and integrity of user accounts and data, potentially leading to non-compliance with these regulations.

However, exploitation requires prior compromise of a reset token, and the vulnerability does not allow bypassing authentication or discovery of tokens independently.

The issue was fixed in version 4.81.0, and until patched, affected users should wait for token expiration or contact administrators to invalidate active sessions to mitigate risks.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart