Fleet has a rate limiting bypass via untrusted client IP headers

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-24000: 0.43% estimated exploitation activity in the next 30 days; percentile 37.25 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

14 May 2026, 13:13 UTC

Last modified by the source

6 Sep 2026, 07:01 UTC

Source last checked

26 Oct 2026, 15:29 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-j8h8-75h3-jg53

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-24000

Advisory: Fleet has a rate limiting bypass via untrusted client IP headers
IDs: CVE-2026-24000, GHSA-j8h8-75h3-jg53
Record: https://patchnext.com/advisories/cve-2026-24000 (revision 1, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/fleetdm/fleet/v4 4.80.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/fleetdm/fleet/v4: affected < 4.80.1; fixed in 4.80.1

## Suggested inspection (read-only)
- Go github.com/fleetdm/fleet/v4: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/fleetdm/fleet/v4.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-j8h8-75h3-jg53 (GitHub-reviewed advisory GHSA-j8h8-75h3-jg53 lists affected ranges: Go github.com/fleetdm/fleet/v4 >=0 <4.80.1)

Commands are suggestions: review each one before running it.