Cross-team policy disclosure via nil-scope authorization
Published Aug 26, 2026 · Updated Aug 26, 2026
Incorrect authorization in Fleet before 4.85.0 allows remote authenticated users to read other teams' policy details through the global API. The GetPolicyByIDQueries handler authorizes an empty policy with a nil TeamID, then fetches a sequential policy ID without a team filter or post-fetch scope check. Observer-level access on any team is sufficient to enumerate other teams' policy queries, compliance counts, and installer or script metadata.
Summary
What happened
Incorrect authorization in Fleet before 4.85.0 allows remote authenticated users to read other teams' policy details through the global API. The GetPolicyByIDQueries handler authorizes an empty policy with a nil TeamID, then fetches a sequential policy ID without a team filter or post-fetch scope check. Observer-level access on any team is sufficient to enumerate other teams' policy queries, compliance counts, and installer or script metadata.
The record
- CVE
- CVE-2026-41262
- Published
- Aug 26, 2026
- Updated
- Aug 26, 2026
- Vendor
- Fleet Device Management
- Product
- Fleet
- Classifications
- CWE-863, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 26, 2026CVE publishedPublication date reported by the CVE source.
- Aug 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.85.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- GitHub advisory HTTP-request proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo