Skip to main content
VulnerabilityPublished

CVE-2026-25963: fleetdm fleet · Incorrect Authorization

Affects fleetdm fleetSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 1.2 Low : upgrade to 4.80.1 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
1.2Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.80.1
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade fleet and fleetdm/fleet to 4.80.1.

Affected software

ProductAffectedFixed in
fleetdmfleetAffected
  • <4.80.1
Fixed in
  • 4.80.1
GitHubfleetdm/fleetpkg:github/fleetdm/fleetOther threatsAffected
  • <4.80.1
Fixed in
  • 4.80.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The definitive mitigation is to upgrade Fleet to version 4.80.1 or later, where the authorization check is properly enforced. If immediate upgrading is not feasible, organizations should implement strict access controls by limiting certificate template management permissions to highly trusted users only. Avoid delegating team administrator privileges unless absolutely necessary, and regularly audit team administrator roles and actions. Additionally, monitoring deletion API calls and certificate template inventories can help detect unauthorized deletions early. Implementing role-based access controls (RBAC) with the principle of least privilege and segregating teams to minimize cross-team administrative overlap will further reduce risk. Finally, organizations should maintain backups of certificate templates to enable recovery in case of accidental or malicious deletions.

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.

References

Community reviews

Loading reviews…