NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

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

mediumCVSS 4.0 6.0GHSA-3458-r943-hmx4

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.

Published Mar 27, 2026 · Updated Apr 1, 2026

Affected packages

github.com/fleetdm/fleet/v4

Ecosystem
Go
Affected
< 4.43.5-0.20260113202849-bbc1aef2987d
Fixed in
4.43.5-0.20260113202849-bbc1aef2987d
Check
go list -m github.com/fleetdm/fleet/v4

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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 [[email protected]](mailto:[email protected]) Join #fleet in osquery Slack

Credits

Fleet thanks @fuzzztf for responsibly reporting this issue.

Credited to fuzzztf.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Go vulnerabilities

All Go entries