github.com/fleetdm/fleet/v4
Affected
- introduced
0, fixed4.80.1(semver)
Fixed versions
4.80.1
Fix
- Fixed version
4.80.1go get github.com/fleetdm/fleet/[email protected]
Advisory
Also known as: CVE-2026-46356, GO-2026-5520
Fleet: IP spoofing allows bypassing API rate limiting
Summary
A vulnerability in Fleet's IP extraction logic allows unauthenticated attackers to bypass API rate limiting by spoofing client IP headers. This may allow brute-force login attempts or other abuse against Fleet instances exposed to the public internet.
Impact
Fleet extracted client IP addresses from request headers (True-Client-IP, X-Real-IP, X-Forwarded-For) without validating that those headers originate from a trusted proxy. The extracted IP is used as the key for rate limiting and IP ban decisions.
As a result, an attacker could rotate the value of these headers on each request, causing Fleet to treat each attempt as coming from a different client. This effectively bypasses per-IP rate limits on sensitive endpoints such as the login API, enabling unrestricted brute-force or credential stuffing attacks.
This issue primarily affects Fleet instances that are directly exposed to the internet without a reverse proxy that overwrites forwarded-IP headers. Instances behind a properly configured proxy or WAF are less affected.
Workarounds
If an immediate upgrade is not possible, administrators should ensure Fleet is deployed behind a reverse proxy (e.g., nginx, Cloudflare, AWS ALB) that overwrites X-Forwarded-For with the true client IP, and apply rate limiting at the proxy or WAF layer.
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.
Medium Basis: The source's own band: MODERATE
0, fixed 4.80.1 (semver)4.80.1
4.80.1go get github.com/fleetdm/fleet/[email protected]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
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0