# CVE-2026-26060: GO-2026-4888 - Fleet: Password reset tokens remain valid after password change for 24 hours in github.com/fleetdm/fleet

Source: https://junglewise.ai/threats/cve-2026-26060-fleet-password-reset-tokens-remain-valid-after-password-change  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-03-27  
License: CC BY 4.0 with a link back

CVE-2026-26060 · Severity: high · CVSS 8.8 · Published 2026-03-27

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.

Technologies: [Fleetdm Fleet](https://junglewise.ai/threats/technologies/fleetdm-fleet), [github.com/fleetdm/fleet/v4 (Go)](https://junglewise.ai/threats/technologies/github-com-fleetdm-fleet-v4). Vendors: [Fleetdm](https://junglewise.ai/threats/vendors/fleetdm), [Go](https://junglewise.ai/threats/vendors/go).

## Quick answers

**Is CVE-2026-26060 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-26060 being exploited in the wild.

**How severe is CVE-2026-26060?** High severity, with a CVSS score of 8.8, published 27 March 2026.

**Which products and versions are affected?** github.com/fleetdm/fleet/v4 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=4.43.5-0.20260113202849-bbc1aef2987d.

**Is there a fix for CVE-2026-26060?** Yes. github.com/fleetdm/fleet/v4 (Go): upgrade to 4.43.5-0.20260113202849-bbc1aef2987d or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2026-26060?** Check whether you run Fleetdm Fleet or github.com/fleetdm/fleet/v4 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/fleetdm/fleet/v4 (Go): upgrade to 4.43.5-0.20260113202849-bbc1aef2987d or later

  ```sh
  go get github.com/fleetdm/fleet/v4@v4.43.5-0.20260113202849-bbc1aef2987d
  ```


## Affected products

- Fleetdm Fleet
- github.com/fleetdm/fleet/v4 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=4.43.5-0.20260113202849-bbc1aef2987d

## Identifiers

- CVE-2026-26060
- GHSA-3458-r943-hmx4
- GO-2026-4888

## Related threats

- [Fleet SQL injection in Okta conditional access endpoint](https://junglewise.ai/threats/cve-2026-54245-fleet-sql-injection-in-okta-conditional-access-endpoint)
- [Fleet SQL injection in Apple MDM commands endpoint](https://junglewise.ai/threats/cve-2026-46371-fleet-sql-injection-in-apple-mdm-commands-endpoint)
- [Fleet SQL injection in labels host-listing endpoint](https://junglewise.ai/threats/cve-2026-46370-fleet-sql-injection-in-labels-host-listing-endpoint)
- [Fleet information disclosure in target search endpoint](https://junglewise.ai/threats/cve-2026-48786-fleet-information-disclosure-in-target-search-endpoint)
- [Fleet DM cross-team policy data exposure in global policy endpoint](https://junglewise.ai/threats/cve-2026-41262-fleet-dm-cross-team-policy-data-exposure-in-global-policy)