Is CVE-2026-26062 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-26062 being exploited in the wild.

How severe is CVE-2026-26062?

High severity, with a CVSS score of 6.5, published 14 May 2026.

Which products and versions are affected?

github.com/fleetdm/fleet/v4 (Go) < 4.81.0, SEMVER:introduced=0,fixed=4.81.0.

Is there a fix for CVE-2026-26062?

Yes. github.com/fleetdm/fleet/v4 (Go): upgrade to 4.81.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-26062 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-26062?

Check whether you run github.com/fleetdm/fleet/v4 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-26062: Fleet Device Management DoS in gRPC PublishLogs endpoint

Q: Is there a fix for CVE-2026-26062?

Yes. github.com/fleetdm/fleet/v4 (Go): upgrade to 4.81.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-26062 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-26062?

Check whether you run github.com/fleetdm/fleet/v4 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-26062 · Severity: high · CVSS 6.5 · Published 2026-05-14

Fleet is an open-source platform used by IT and security teams to manage and monitor laptops, servers, and other devices. A vulnerability in the server's log-processing component allows an attacker to crash the Fleet server by sending a single malicious request. This results in a total service outage, preventing administrators from managing their device fleet until the system is restored.

Technologies: github.com/fleetdm/fleet/v4 (Go). Vendors: Go.

Quick answers

Is CVE-2026-26062 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-26062 being exploited in the wild.
How severe is CVE-2026-26062?: High severity, with a CVSS score of 6.5, published 14 May 2026.
Which products and versions are affected?: github.com/fleetdm/fleet/v4 (Go) < 4.81.0, SEMVER:introduced=0,fixed=4.81.0.
Is there a fix for CVE-2026-26062?: Yes. github.com/fleetdm/fleet/v4 (Go): upgrade to 4.81.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-26062 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-26062?: Check whether you run github.com/fleetdm/fleet/v4 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/fleetdm/fleet/v4 (Go): upgrade to 4.81.0 or later
```
go get github.com/fleetdm/fleet/v4@v4.81.0
```

Technical details

A denial-of-service (DoS) vulnerability exists in the Fleet server's gRPC Launcher 'PublishLogs' endpoint due to improper input validation (CWE-20). The server fails to gracefully handle certain unexpected input values, leading to a process termination (crash). An attacker with a valid enrolled Launcher node key can trigger this crash by sending a single crafted gRPC request. While the attack requires authentication (a node key), it results in a complete loss of availability for the Fleet management console. The issue is resolved in version 4.81.0.

Affected products

Fleet Device Management (fleetdm) Fleet < 4.81.0

Identifiers

CVE-2026-26062
GHSA-x67p-9m2r-fxqv
GO-2026-5744

Timeline

2026-02-20: patched: Version 4.81.0 released
2026-05-13: advisory: GitHub Security Advisory published
2026-05-14: disclosed: CVE published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.