CVE-2026-48786: Infoleak

Published Aug 12, 2026
·
Updated

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 Join #fleet in osquery Slack

Affected Software

1 affected componentFixes available
go/github.com/fleetdm/fleet/v4<4.87.0
4.87.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade go/github.com/fleetdm/fleet/v4 to a version that resolves this vulnerability.

    Fixed in 4.87.0
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in v4.87.0
  3. Configuration

    Restrict Observer, Observer+, and Technician roles (global or team-scoped) to fully trusted users until the patch is applied.

    Fleet roles and access control Restrict Observer and Technician roles = fully trusted users only
  4. Operational

    Rotate any credentials stored in team agent options (including AWS keys, proxy passwords, and session tokens) because those values were exposed.

  5. Operational

    Rotate team enroll secrets for any team that may have been exposed.

Event History

Aug 12, 2026
Advisory Published
via GitHub·03:18 PM
Data Sourced
via GitHub·03:18 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-48786?

The severity of CVE-2026-48786 is rated as medium with a score of 6.5.

2

What does CVE-2026-48786 affect?

CVE-2026-48786 affects the target search endpoint of the FleetDM software.

3

What is the primary issue with CVE-2026-48786?

CVE-2026-48786 presents an info leak by returning sensitive team configuration data to unauthorized users.

4

How can I fix CVE-2026-48786?

To fix CVE-2026-48786, update to the latest version of FleetDM that addresses the vulnerability.

5

Who should be concerned about CVE-2026-48786?

Any organization using FleetDM software, especially those with observer-class users, should be concerned about CVE-2026-48786.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203