Fleet DM Vulnerable to Cross-Team Policy Data Exposure via Global Policy Read Endpoint

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2026-41262: 0.30% estimated exploitation activity in the next 30 days; percentile 23.34 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The global policy read endpoint (GET /api/latest/fleet/policies/{policyid}) performs authorization against an empty fleet.Policy{} struct with nil TeamID, then fetches any policy by ID from the database without verifying the fetched policy actually belongs to the global scope. This allows a user with observer-level access on any single team to read the full details of policies belonging to any other team, bypassing Fleet's team isolation model. Details The vulnerability is in GetPolicyByIDQueries at server/service/globalpolicies.go:163-180: The authorization passes because the OPA rule at server/authz/policy.rego:724-728 allows reading policies with null teamid for any user who holds a role on any team: Since the auth object has nil TeamID, this rule fires for any team member. After authorization, ds.Policy() calls policyDB() at server/datastore/mysql/policies.go:283-288 with a nil teamID: This returns any policy regardless of team ownership, and the full policy object is…

Published by the source

26 Jun 2026, 20:30 UTC

Last modified by the source

26 Jun 2026, 20:30 UTC

Source last checked

26 Oct 2026, 15:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-gm7f-v959-fr2g

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-41262

Advisory: Fleet DM Vulnerable to Cross-Team Policy Data Exposure via Global Policy Read Endpoint
IDs: CVE-2026-41262, GHSA-gm7f-v959-fr2g
Record: https://patchnext.com/advisories/cve-2026-41262 (revision 1, source checked 26 Oct 2026, 15:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/fleetdm/fleet/v4 4.85.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/fleetdm/fleet/v4: affected < 4.85.0; fixed in 4.85.0

## Suggested inspection (read-only)
- Go github.com/fleetdm/fleet/v4: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/fleetdm/fleet/v4.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-gm7f-v959-fr2g (GitHub-reviewed advisory GHSA-gm7f-v959-fr2g lists affected ranges: Go github.com/fleetdm/fleet/v4 >=0 <4.85.0)

Commands are suggestions: review each one before running it.