CVE-2026-25963 Fleet: Authorization Bypass in certificate template batch deletion for team administrators
A team administrator can delete certificate templates belonging to other teams due to a missing ownership check, disrupting device enrollment and authentication workflows.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-25963?
CVE-2026-25963 is a low-severity missing authorization vulnerability in fleetdm fleet, published on 26 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Official description
Fleet is open source device management software. In versions prior to 4.80.1, a broken authorization check in Fleet’s certificate template deletion API could allow a team administrator to delete certificate templates belonging to other teams within the same Fleet instance. Fleet supports certificate templates that are scoped to individual teams. In affected versions, the batch deletion endpoint validated authorization using a user-supplied team identifier but did not verify that the certificate template IDs being deleted actually belonged to that team. As a result, a team administrator could delete certificate templates associated with other teams, potentially disrupting certificate-based workflows such as device enrollment, Wi-Fi authentication, VPN access, or other certificate-dependent configurations for the affected teams. This issue does not allow privilege escalation, access to sensitive data, or compromise of Fleet’s control plane. Impact is limited to integrity and availability of certificate templates across teams. Version 4.80.1 patches the issue. If an immediate upgrade is not possible, administrators should restrict access to certificate template management to trusted users and avoid delegating team administrator permissions where not strictly required.
Weakness: CWE-863
Which versions are affected by CVE-2026-25963?
3 open source packages ship an affected version, including github.com/fleetdm/fleet/v4. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/fleetdm/fleet/v4 Go | All versions | 4.80.1 |
github.com/fleetdm/fleet/v4 Go | All versions | 4.80.1 |
github.com/fleetdm/fleet/v4 Go | All versions | 4.80.1 |
Products include Fleetdm Fleet.
How do I fix CVE-2026-25963?
Upgrade github.com/fleetdm/fleet/v4 to 4.80.1 or later.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-25963 being exploited?
There is no known exploitation of CVE-2026-25963 in the wild and no public exploit code.
Other vulnerabilities in fleetdm fleet
- CVE-2020-26276 SAML authentication vulnerability in Fleet
- CVE-2026-103264 Fleet before 4.87.0 Authentication Bypass via Device Identifiers
- CVE-2026-23518 Fleet has a JWT signature bypass vulnerability in Azure AD MDM enrollment
- CVE-2026-26062 Fleet server may terminate unexpectedly when handling certain gRPC requests
- CVE-2026-26061 Fleet's unbounded request body read allows remote Denial of Service
Sources
Also known as GHSA-5jvp-m9h4-253h, GO-2026-4561.