Fleet has an Access Control vulnerability in debug/pprof endpoints

Summary

Fleet is open source device management software. A broken access control issue in versions prior to 4.78.3, 4.77.1, 4.76.2, 4.75.2, and 4.53.3 allowed authenticated users to access debug and profiling endpoints regardless of role. As a result, low-privilege users could view internal server diagnostics and trigger resource-intensive profiling operations. Fleet’s debug/pprof endpoints are accessible to any authenticated user regardless of role, including the lowest-privilege “Observer” role. This allows low-privilege users to access sensitive server internals, including runtime profiling data and in-memory application state, and to trigger CPU-intensive profiling operations that could lead to denial of service. Versions 4.78.3, 4.77.1, 4.76.2, 4.75.2, and 4.53.3 fix the issue. If an immediate upgrade is not possible, users should put the debug/pprof endpoints behind an IP allowlist as a workaround.

Timeline

1. Jan 21, 2026, 9:45 PM UTCCVE published
2. Jan 22, 2026, 3:10 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: total

3. Jan 22, 2026, 4:49 PM UTCRecord last updated

Affected versions

• fleetdm fleet

  From 4.78.0 · fixed in 4.78.3; From 4.77.0 · fixed in 4.77.1; From 4.76.0 · fixed in 4.76.2; From 4.75.0 · fixed in 4.75.2; fixed in 4.53.3

• github.com/fleetdm/fleet/v4Go

  From 4.75.0 · fixed in 4.75.2; From 4.76.0 · fixed in 4.76.2; From 4.77.0 · fixed in 4.77.1; From 4.78.0 · fixed in 4.78.3

• github.com/fleetdm/fleetGo

  From 4.78.0 · fixed in 4.78.3

• github.com/fleetdm/fleetGo

  From 4.77.0 · fixed in 4.77.1

• github.com/fleetdm/fleetGo

  From 4.76.0 · fixed in 4.76.2

• github.com/fleetdm/fleetGo

  From 4.75.0 · fixed in 4.75.2

• github.com/fleetdm/fleet/v4Go

  fixed in 4.78.3-0.20260112221730-5c030e32a3a9

References 2