HighGHSA-x67p-9m2r-fxqvCVE-2026-26062GO-2026-5744

Fleet server may terminate unexpectedly when handling certain gRPC requests

Published 14 May 2026 · Updated 25 Jun 2026

Is your project on an affected github.com/fleetdm/fleet/v4?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<4.81.0
Fixed in
4.81.0
Update to the fixed version for your release line, for example:go get github.com/fleetdm/fleet/v4@v4.81.0

Details

Summary

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.

Impact

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
  • No integrity impact

Workarounds

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.
  • Monitor for repeated Fleet process crashes or unexpected restarts indicating potential exploitation.

For More Information

If you have any questions or concerns about this advisory, please contact us at:

Email us at [security@fleetdm.com](mailto:security@fleetdm.com)

Credits

We thank @fuzzztf for responsibly reporting this issue.

Is GHSA-x67p-9m2r-fxqv in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/fleetdm/fleet/v4, and gives you the command that fixes it.

More advisories for github.com/fleetdm/fleet/v4

  • LowCVE-2026-54245Fleet: SQL injection in Okta conditional access endpoint allows host-controlled compromise of the Fleet database in github.com/fleetdm/fleet · 25 Aug 2026
  • LowCVE-2026-101047Fleet: Unauthenticated download of in-house iOS app binaries via predictable URLs in github.com/fleetdm/fleet · 25 Aug 2026
  • LowCVE-2026-101046Fleet: ORDER BY column injection on activity list endpoints in github.com/fleetdm/fleet · 25 Aug 2026
  • LowCVE-2026-101046Fleet: ORDER BY column injection on activity list endpoints · 20 Aug 2026
  • MediumCVE-2026-101047Fleet: Unauthenticated download of in-house iOS app binaries via predictable URLs · 20 Aug 2026
  • LowCVE-2026-48786Fleet: Observer-class users can view team enroll secrets and credential-bearing configuration via target search endpoint in github.com/fleetdm/fleet · 18 Aug 2026
All 59 advisories for github.com/fleetdm/fleet/v4

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.