VulnerabilityPublished 26 Jun 2026

CVE-2026-41262: V4 · Fleet DM Vulnerable to Cross-Team Policy Data Exposure via Global Policy Read Endpoint

Affects github.com/fleetdm/fleet/v4Source GCVE Database

Compare

Authoritative record:CVE-2026-41262· Medium 4.3

Not known to be exploited · CVSS 4.3 Medium : upgrade to 4.85.0 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.85.0

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 26 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CISA SSVC: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE ID reserved
by GitHub, Inc.
18 Apr 202614:01 UTC, 130 days before disclosure
CVE published
on cve.org
26 Aug 202618:32 UTC, t = 0
CISA SSVC assessment
proof of concept public
26 Aug 202618:57 UTC, 25 minutes after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA SSVC, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade github.com/fleetdm/fleet/v4 to 4.85.0.

Affected software

Product	Affected	Fixed in
Gogithub.com/fleetdm/fleet/v4	Affected <4.85.0	Fixed in 4.85.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Fleet to version 4.85.0 or later, where this vulnerability is fixed. The patch ensures proper verification of team ownership before returning policy details. Until upgrading, restrict observer-level access to trusted users only. Patch status is confirmed as available and official.

Description

Fleet versions prior to 4.85.0 have a vulnerability in the global policy read endpoint that allows authenticated users with observer-level access on any team to read policy details from other teams. This occurs because the endpoint does not verify team ownership and returns policy data without proper scope checks. The flaw allows enumeration of policy IDs to access sensitive policy SQL queries and related metadata across team boundaries. The issue is fixed in version 4.85.0.

Impact

An authenticated user with observer-level access on any single team can access detailed policy information belonging to other teams, violating Fleet's team isolation model. This exposure includes sensitive security-monitoring queries and compliance data, potentially aiding attackers in understanding and circumventing security controls. The vulnerability does not allow modification or denial of service but leaks confidential policy data.

Summary

Fleet, an open-source device management platform, contains an access control vulnerability (CVE-2026-41262) in versions before 4.85.0. The global policy read endpoint (GET /api/latest/fleet/policies/{policy_id}) fails to verify that the requesting user’s team matches the team owning the requested policy. Authorization is incorrectly performed against an empty policy object with a nil TeamID, allowing any user with a role on any team to access policies from other teams. Since policy IDs are sequential, an attacker can enumerate them to retrieve policy SQL queries, host pass/fail counts, and associated software installer and script metadata. This exposure leaks security-monitoring strategies and compliance posture across team boundaries. The vulnerability is addressed in Fleet version 4.85.0.

CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Sep 2026, 22:33 UTC

WeaknessesCWE-863

Technical details

References

Community reviews

Related threats