CVE-2026-46356: 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.
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).
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.
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 entriesGHSA-q9c5-pp7m-fm2g
Fleet: Unauthenticated download of in-house iOS app binaries via predictable URLs
medium5.3Aug 20, 2026GHSA-rxhg-vcww-2mpw
Fleet: ORDER BY column injection on activity list endpoints
low3.1Aug 20, 2026CVE-2026-48786
Fleet: Observer-class users can view team enroll secrets and credential-bearing configuration via target search endpoint
medium6.5Aug 12, 2026CVE-2026-41262
Fleet DM Vulnerable to Cross-Team Policy Data Exposure via Global Policy Read Endpoint
medium4.3Jun 26, 2026CVE-2026-46370
Fleet has observer-level enrollment secret extraction via ORDER BY oracle on labels host-listing endpoint
medium6.5Jun 12, 2026CVE-2026-46371
Fleet: Observer-level enrollment secret extraction via ORDER BY oracle on Apple MDM commands endpoint
medium6.5Jun 12, 2026
