CVE-2026-48786

Ein Angreifer kann mehrere Schwachstellen in Fleet ausnutzen, um SQL-Injection durchzuführen, beliebigen Code auszuführen, Daten zu manipulieren oder vertrauliche Informationen offenzulegen.

### Summary The target search endpoint (`POST /api/latest/fleet/targets`) returned team enroll secrets and full team configuration, including credential-bearing agent options, to observer-class users. Other team-facing endpoints mask these fields for observers; the target search endpoint did not apply the same sanitization. ### Impact An authenticated user with Observer, Observer+, or Technician role (global or team-scoped) could retrieve unmasked team enroll secrets and team agent options by performing a target search against an observer-runnable query. With a leaked team enroll secret, an attacker could enroll unauthorized hosts into the affected team. If the team's agent options contained credentials such as AWS secret access keys or proxy passwords, those values were also exposed. ### Patches - v4.87.0 ### Workarounds If an immediate upgrade is not possible, administrators should: - Rotate team enroll secrets for any team that may have been exposed - Rotate any credentials stored in team agent options (AWS keys, proxy passwords, session tokens) - Restrict Observer and Technician roles to fully trusted users until the patch is applied ### Credits Fleet thanks @fuzzztf for responsibly reporting this issue. ### For more information If there are any questions or comments about this advisory: Send an email to [security@fleetdm.com](mailto:security@fleetdm.com) Join #fleet in [osquery Slack](https://join.slack.com/t/osquery/shared_invite/zt-h29zm0gk-s2DBtGUTW4CFel0f0IjTEw)

Fleet: Observer-class users can view team enroll secrets and credential-bearing configuration via target search endpoint in github.com/fleetdm/fleet