dbcve.org
FleetApplication · Fleetdm

CVE-2026-25963

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-26
Fix available
A fix is available. Upgrade to 4.80.1 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A broken authorization check in Fleet's certificate template batch deletion API allows team administrators to delete certificate templates from other teams. The endpoint validates authorization using a user-supplied team identifier but fails to verify that the certificate template IDs being deleted actually belong to that team, enabling cross-team deletion.

MitigationUpgrade to Fleet 4.80.1 to patch the vulnerability. If immediate upgrade is not possible, restrict access to certificate template management to trusted users and avoid delegating team administrator permissions where not strictly required.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FleetApplication
Affected:< 4.80.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Fleet version
    Run 'fleetctl version' or check the Fleet UI under the Settings or My Account section to determine the installed version number
    Affected if The installed version is below 4.80.1 (e.g., 4.80.0, 4.79.x, or earlier)
  2. Confirm certificate templates are configured
    Access the Fleet UI and navigate to the certificate template management section, or query the API for existing certificate templates
    Affected if There are one or more certificate templates defined in the Fleet instance
  3. Verify team administrator roles exist
    Check the Teams section in Fleet UI or query the team membership API to identify users with team administrator permissions
    Affected if There are team administrators configured, particularly for teams that own certificate templates
  4. Inspect API access logs for cross-team deletion attempts
    Review Fleet's API audit logs or server logs for DELETE requests to the certificate template batch deletion endpoint, noting the team ID supplied versus the actual ownership of the templates
    Affected if There are deletion API calls where the team ID in the request does not match the team ID associated with the certificate template being deleted

You are affected if Fleet version is below 4.80.1, certificate templates are configured in your instance, and team administrators exist who could potentially delete templates from teams they do not own.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.80.1 or later
Fixed in 4.80.1
Interim mitigation

Upgrade to Fleet 4.80.1 to patch the vulnerability. If immediate upgrade is not possible, restrict access to certificate template management to trusted users and avoid delegating team administrator permissions where not strictly required.

Recommended fix Moderate confidence

4.80.1

  1. Upgrade Fleet to version 4.80.1 or later to apply the authorization fix
  2. After upgrading, verify that certificate templates are correctly scoped to their respective teams
  3. Review user permissions and restrict access to certificate template management to only trusted administrators
  4. Audit existing certificate templates to ensure no unauthorized deletions occurred prior to the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fleet Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25963 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-25963 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data