CVE-2026-26060: Fleet: Password reset tokens remain valid after password change for 24 hours

Published Mar 27, 2026
·
Updated

Summary

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.

Impact

If an attacker had prior access to a valid password reset token, they could reuse that token within its validity window to reset the user’s password after the user has already changed it. This could result in temporary account takeover.

Exploitation requires prior compromise of a password reset token and is further constrained by the token’s 24-hour expiration period. The issue does not allow discovery of reset tokens, does not bypass authentication on its own, and does not affect accounts without an existing valid reset token.

Workarounds

Until patched, users who believe a password reset token may have been exposed should wait for the token to expire before reusing the account, or contact a Fleet administrator to invalidate active sessions.

For more information

If there are any questions or comments about this advisory:

Email Fleet at security@fleetdm.com Join #fleet in osquery Slack

Credits

Fleet thanks @fuzzztf for responsibly reporting this issue.

Other sources

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.

MITRE

Affected Software

2 affected componentsFixes available
go/github.com/fleetdm/fleet/v4<4.43.5-0.20260113202849-bbc1aef2987d
4.43.5-0.20260113202849-bbc1aef2987d
fleetdm fleet<4.81.0

Event History

Mar 27, 2026
Advisory Published
via GitHub·06:17 PM
Data Sourced
via GitHub·06:17 PM
DescriptionWeaknessAffected Software
CVE Published
via MITRE·06:22 PM
Data Sourced
via MITRE·06:22 PM
DescriptionWeakness
Data Sourced
via NVD·07:16 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-26060?

CVE-2026-26060 is classified as a medium severity vulnerability due to the risk of unauthorized access using stale password reset tokens.

2

How do I fix CVE-2026-26060?

To fix CVE-2026-26060, update Fleet to version 4.43.5-0.20260113202849-bbc1aef2987d or later.

3

What impact does CVE-2026-26060 have on users?

CVE-2026-26060 can allow attackers to use old password reset tokens to gain unauthorized access to user accounts.

4

Is CVE-2026-26060 a common vulnerability?

CVE-2026-26060 highlights a common mistake in password management systems regarding token expiration.

5

How can I verify if my version of Fleet is vulnerable to CVE-2026-26060?

Check your Fleet version against the specified vulnerable version to determine if you are using an affected version related to CVE-2026-26060.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203