dbcve.org
FleetApplication · Fleetdm

CVE-2026-26062

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-14
Fix available
A fix is available. Upgrade to 4.81.0 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. Prior to version 4.81.0, Fleet contained a denial-of-service (DoS) issue in the gRPC Launcher `PublishLogs` endpoint. In affected versions, certain unexpected input values were not handled gracefully, which could cause the Fleet server process to terminate while processing an authenticated request from an enrolled Launcher host. An authenticated attacker with access to any enrolled Launcher node key could cause an immediate and complete denial of service by sending a single gRPC request to the `PublishLogs` endpoint. This vulnerability impacts availability only. There is no exposure of sensitive data, no authentication bypass, no privilege escalation, and no integrity impact. Version 4.81.0 contains a patch. If upgrading immediately is not possible, the following mitigations can reduce exposure. Restrict network access to the Fleet gRPC endpoint where feasible (for example, limiting inbound access to known host IP ranges); deploy Fleet behind infrastructure that terminates or filters gRPC traffic if Launcher log ingestion is not required; and/or monitor for repeated Fleet process crashes or unexpected restarts indicating potential exploitation.

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

Fleet's gRPC Launcher PublishLogs endpoint fails to handle certain unexpected input values gracefully, causing the Fleet server process to terminate. An attacker with a valid enrolled Launcher node key can send a single crafted gRPC request that crashes the entire Fleet server, resulting in complete availability loss.

MitigationUpgrade to Fleet version 4.81.0 or later. If immediate upgrade is not possible, restrict network access to the gRPC endpoint, deploy Fleet behind infrastructure that filters gRPC traffic if log ingestion is not required, and monitor for unexpected Fleet process crashes.

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

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 server version
    Run 'fleet --version' or check the Fleet UI/Docker container version to determine the installed Fleet version
    Affected if Installed version is below 4.81.0
  2. Verify gRPC Launcher is enabled
    Check Fleet configuration for gRPC settings - look for 'grpc' or 'launcher' configuration options in Fleet's config file or environment variables
    Affected if gRPC and Launcher functionality are enabled and exposed
  3. Confirm Launcher node enrollment is active
    Review Launcher enrollment status in Fleet - check if there are enrolled Launcher nodes with valid node keys in the Fleet database or UI
    Affected if There are actively enrolled Launcher nodes with valid node keys
  4. Assess gRPC endpoint network exposure
    Review network configuration to determine if the gRPC endpoint (typically port 8080) is accessible from untrusted networks
    Affected if The gRPC endpoint is exposed to network segments accessible by potential attackers with compromised Launcher keys

A user is affected if their Fleet version is below 4.81.0 AND gRPC Launcher functionality is enabled with enrolled Launcher nodes that could send crafted PublishLogs requests.

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.81.0 or later
Fixed in 4.81.0
Interim mitigation

Upgrade to Fleet version 4.81.0 or later. If immediate upgrade is not possible, restrict network access to the gRPC endpoint, deploy Fleet behind infrastructure that filters gRPC traffic if log ingestion is not required, and monitor for unexpected Fleet process crashes.

Recommended fix High confidence

Fleet version 4.81.0

  1. Verify current Fleet version by checking the Fleet server or using `fleetctl version`
  2. Plan for upgrade following standard Fleet upgrade procedures
  3. Upgrade Fleet to version 4.81.0 or later
  4. Verify the upgrade was successful by checking the Fleet version
  5. Monitor Fleet process stability and check logs for any crashes

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

Fix this in Fleet Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-26062 — 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-26062 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