Summary
Fleet: Observer-class users can view team enroll secrets and credential-bearing configuration via target search endpoint
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.
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 [email protected]
Join #fleet in osquery Slack
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.
CVE-2026-48786 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.87.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
- v4.87.0
Frequently Asked Questions
- What is CVE-2026-48786? CVE-2026-48786 is a medium-severity security vulnerability in github.com/fleetdm/fleet/v4 (go), affecting versions < 4.87.0. It is fixed in 4.87.0.
- How severe is CVE-2026-48786? CVE-2026-48786 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of github.com/fleetdm/fleet/v4 are affected by CVE-2026-48786? github.com/fleetdm/fleet/v4 (go) versions < 4.87.0 is affected.
- Is there a fix for CVE-2026-48786? Yes. CVE-2026-48786 is fixed in 4.87.0. Upgrade to this version or later.
- Is CVE-2026-48786 exploitable, and should I be worried? Whether CVE-2026-48786 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-48786 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-48786? Upgrade
github.com/fleetdm/fleet/v4to 4.87.0 or later.