NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

CVE-2026-24000: Fleet has a rate limiting bypass via untrusted client IP headers

mediumCVSS 4.0 6.9 · 3.1 5.3GHSA-j8h8-75h3-jg53

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.

Published May 14, 2026 · Updated Sep 6, 2026

Affected packages

github.com/fleetdm/fleet/v4

Ecosystem
Go
Affected
< 4.80.1
Fixed in
4.80.1
Check
go list -m github.com/fleetdm/fleet/v4

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

Credited to fuzzztf.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Go vulnerabilities

All Go entries