Advisory

GHSA-j8h8-75h3-jg53

Also known as: CVE-2026-24000, GO-2026-5455

Summary

Fleet has a rate limiting bypass via untrusted client IP headers

Details

Impact

Fleet trusted client-supplied IP address headers when determining the source IP for incoming requests. This allowed authenticated and unauthenticated clients to spoof their apparent IP address and bypass per-IP rate limiting controls.

Fleet determines a client’s public IP address using HTTP headers such as:

  • X-Forwarded-For
  • X-Real-IP
  • True-Client-IP

These headers were trusted without validation. An attacker could supply arbitrary values in these headers, causing Fleet to treat each request as originating from a different IP address.

This could allow an attacker to bypass per-IP rate limits and increase the effectiveness of brute-force or password-spraying attempts against authentication endpoints.

This issue does not allow authentication bypass, privilege escalation, data exposure, or remote code execution on its own.

Workarounds

Run Fleet behind a trusted reverse proxy or load balancer that overwrites client IP headers.

For more information

If you have any questions or comments about this advisory:

Email us at [[email protected]](mailto:[email protected])
Join #fleet in osquery Slack

Credits

We thank @fuzzztf for responsibly reporting this issue.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-05-14 13:13 UTC
Modified
2026-06-25 23:11 UTC

Affected packages and fixes

github.com/fleetdm/fleet/v4

Go · All systems

Affected

  • introduced 0, fixed 4.80.1 (semver)

Fixed versions

4.80.1

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences