How severe is GHSA-x67p-9m2r-fxqv?

No CVSS score has been assigned to GHSA-x67p-9m2r-fxqv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-x67p-9m2r-fxqv?

GHSA-x67p-9m2r-fxqv affects the following packages: github.com/fleetdm/fleet/v4 (Go). Ecosystems affected: Go.

How do I fix GHSA-x67p-9m2r-fxqv?

Update github.com/fleetdm/fleet/v4 to 4.81.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x67p-9m2r-fxqv is resolved across your whole dependency graph.

How do I detect GHSA-x67p-9m2r-fxqv in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/fleetdm/fleet/v4, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-x67p-9m2r-fxqv if there is no patch (or I can't update yet)?

Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Is GHSA-x67p-9m2r-fxqv actively exploited in the wild?

No public exploit code has been indexed for GHSA-x67p-9m2r-fxqv yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-x67p-9m2r-fxqv?

GHSA-x67p-9m2r-fxqv has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 43th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-x67p-9m2r-fxqv?

GHSA-x67p-9m2r-fxqv is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-x67p-9m2r-fxqv published, and has it been updated?

GHSA-x67p-9m2r-fxqv was published on May 14, 2026 and was last updated on June 25, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

GHSA-x67p-9m2r-fxqv — v4

GHSA-x67p-9m2r-fxqv is a Improper Input Validation vulnerability in github.com/fleetdm/fleet/v4. A fix is available for github.com/fleetdm/fleet/v4 — see the affected versions and patch details below.

Fleet server may terminate unexpectedly when handling certain gRPC requests

Also known asCVE-2026-26062GO-2026-5744

Published

May 14, 2026

Updated

Jun 25, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 27, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs43th percentile — riskier than 43% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/fleetdm/fleet/v4

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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 [email protected]

Credits

We thank @fuzzztf for responsibly reporting this issue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/fleetdm/fleet/v4`	all versions	4.81.0`go get github.com/fleetdm/fleet/v4@v4.81.0`

Affected Products

1 product · 1 configurations

Application

fleetfleetdm

< 4.81.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/fleetdm/fleet/v4, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/fleetdm/fleet/v4 to 4.81.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x67p-9m2r-fxqv is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Frequently Asked Questions

### 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

O3 Security · Impact-Aware SCA

Is GHSA-x67p-9m2r-fxqv in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

GHSA-x67p-9m2r-fxqv — v4

EPSS Exploitation Probability

Real-World Exposure

Description

Summary

Impact

Workarounds

For More Information

Credits

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-x67p-9m2r-fxqv in your dependencies?