Is CVE-2026-41262 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-41262 being exploited in the wild.

How severe is CVE-2026-41262?

Medium severity, with a CVSS score of 4.3, published 26 August 2026.

Which products and versions are affected?

github.com/fleetdm/fleet/v4 (Go) < 4.85.0, SEMVER:introduced=0,fixed=4.85.0.

Is there a fix for CVE-2026-41262?

Yes. github.com/fleetdm/fleet/v4 (Go): upgrade to 4.85.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-41262 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-41262?

Check whether you run github.com/fleetdm/fleet/v4 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-41262: Fleet DM cross-team policy data exposure in global policy endpoint

Q: Is there a fix for CVE-2026-41262?

Yes. github.com/fleetdm/fleet/v4 (Go): upgrade to 4.85.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-41262 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-41262?

Check whether you run github.com/fleetdm/fleet/v4 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-41262 · Severity: medium · CVSS 4.3 · Published 2026-08-26

Fleet DM, a device management platform, contains a vulnerability that allows users assigned to a specific team to view sensitive security policies belonging to other teams. An attacker with basic observer-level access could read internal SQL queries, compliance data, and script metadata that should be restricted to different departments or clients. This flaw undermines the team isolation model used to keep organizational data separate and secure.

Technologies: github.com/fleetdm/fleet/v4 (Go). Vendors: Go.

Quick answers

Is CVE-2026-41262 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-41262 being exploited in the wild.
How severe is CVE-2026-41262?: Medium severity, with a CVSS score of 4.3, published 26 August 2026.
Which products and versions are affected?: github.com/fleetdm/fleet/v4 (Go) < 4.85.0, SEMVER:introduced=0,fixed=4.85.0.
Is there a fix for CVE-2026-41262?: Yes. github.com/fleetdm/fleet/v4 (Go): upgrade to 4.85.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-41262 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-41262?: Check whether you run github.com/fleetdm/fleet/v4 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/fleetdm/fleet/v4 (Go): upgrade to 4.85.0 or later
```
go get github.com/fleetdm/fleet/v4@v4.85.0
```

Technical details

The vulnerability exists in the `GetPolicyByIDQueries` function within `server/service/global_policies.go`. The endpoint performs an initial authorization check against an empty `fleet.Policy{}` struct (where `TeamID` is nil), which triggers an OPA rule allowing any team member to read global policies. However, the subsequent database fetch retrieves the policy by ID without verifying that the returned object actually belongs to the global scope or the user's authorized team. An attacker with `observer` or higher privileges on any single team can exploit this by sending requests to `GET /api/latest/fleet/policies/{policy_id}` with sequential IDs to enumerate and read sensitive SQL queries, host pass/fail counts, and script metadata across all teams. The issue is addressed in version 4.85.0 by ensuring team-scoped policies cannot be accessed via the global endpoint.

Affected products

Fleet DM Fleet < 4.85.0

Identifiers

CVE-2026-41262
GHSA-gm7f-v959-fr2g
GO-2026-5812

Timeline

2026-06-26: advisory
2026-06-26: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.