Advisory record · GHSA-mxmp-wr3w-rvqx

Fleet: IP spoofing allows bypassing API rate limiting

CVSS 6.9 MediumEPSS 0.0028 · 20th percentile

Published by the GitHub Advisory Database at 14 May 2026, 13:18 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/fleetdm/fleet/v4Go<4.80.14.80.1
Identifiers
GHSA-mxmp-wr3w-rvqx · CVE-2026-46356 · GO-2026-5520
Weakness (CWE)
CWE-290
Published
14 May 2026
Updated
25 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Fleet (Go module github.com/fleetdm/fleet/v4) versions before 4.80.1 trust client IP headers such as True-Client-IP, X-Real-IP and X-Forwarded-For without checking that they come from a trusted proxy, and use the value for rate limiting. An unauthenticated attacker who can reach the instance directly can rotate these headers to evade per-IP rate limits, enabling brute-force or credential stuffing against endpoints such as login. Upgrade to 4.80.1 or later; if upgrading is not possible, place Fleet behind a reverse proxy that overwrites forwarded-IP headers and apply rate limiting there.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.9 Medium 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0028, the 20th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:06 UTC First seen by agentprime
  2. 31 Oct 2026, 15:06 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.