Loading vulnerability…
CVE-2026-41262 is an authorization flaw in Fleet DM affecting the global policy read endpoint (GET /api/latest/fleet/policies/{policy_id}). The endpoint is intended to return only global policies, but insufficient authorization validation allows a user with observer-level access on any team to request arbitrary policy IDs and receive full details for policies belonging to other teams. The issue breaks intended team isolation by failing to ensure that the fetched policy is actually global or otherwise properly authorized in the context of the requesting user. According to the advisory, the recommended fix is to verify after fetch that the returned policy has TeamID == nil before returning it, or to re-authorize against the fetched policy object so team-scoped authorization is correctly enforced.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
GET /api/latest/fleet/policies/{policy_id}), reduce unnecessary low-privilege team memberships, monitor for suspicious sequential enumeration of policy IDs, and apply compensating controls such as API gateway filtering or custom authorization enforcement to block team-scoped users from retrieving non-global policies through the global policy read path.Patch, then assume compromise.
TeamID == nil) before returning it, or alternatively to perform authorization checks against the fetched policy object so that team-scoped access controls are applied correctly.No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.