{"answers":{"affected":"3 open source packages ship an affected version, including github.com/fleetdm/fleet/v4.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41262 exists.","fix":"Upgrade github.com/fleetdm/fleet/v4 to 4.85.0 or later.","what":"CVE-2026-41262 is a medium-severity missing authorization vulnerability in fleetdm fleet, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-41262 and fix it if it is affected.\n\nWhat it is: CVE-2026-41262 is a medium-severity missing authorization vulnerability in fleetdm fleet, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41262 exists.\n\nAffected packages and fixed versions:\n- github.com/fleetdm/fleet/v4 (Go): affected all versions; fixed in 4.85.0\n- github.com/fleetdm/fleet/v4 (Go): affected all versions; fixed in 4.85.0\n- github.com/fleetdm/fleet/v4 (Go): affected all versions; fixed in 4.85.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-41262/ (Markdown: https://insights.sbomify.com/CVE-2026-41262/index.md)","id":"CVE-2026-41262","markdown":"https://insights.sbomify.com/CVE-2026-41262/index.md","name":"CVE-2026-41262","record":{"aliases":["GHSA-gm7f-v959-fr2g","GO-2026-5812"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Device management platform","requires_auth":"low_privilege","summary":"Authenticated users can read other teams' policy details by bypassing team isolation checks in the global policy read endpoint.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"Fleet is an open-source device management platform built on osquery. In versions prior to 4.85.0, the global policy read endpoint (GET /api/latest/fleet/policies/{policy_id}) fails to verify team ownership of the requested policy, allowing an authenticated user with observer-level access on any single team to read the full details of policies belonging to any other team and bypass Fleet's team isolation model. The handler authorizes the request against an empty policy object whose TeamID is nil, which an authorization rule permits for any user holding a role on any team, and then fetches the policy by ID with no team filter and returns it without any post-fetch scope check. Because policy IDs are sequential integers, an attacker can enumerate them to read other teams' policy SQL queries, host pass and fail counts, and associated software-installer and script metadata, exposing security-monitoring strategies and compliance posture across team boundaries. This issue is fixed in version 4.85.0.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Fleet: Cross-Team Policy Data Exposure via Global Policy Read Endpoint","id":"CVE-2026-41262","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"Traefik: BasicAuth middleware: timing side-channel vulnerability","id":"CVE-2026-41263"},"packages":[{"ecosystem":"Go","fixed":["4.85.0"],"introduced":["0"],"last_affected":[],"package":"github.com/fleetdm/fleet/v4","purl":null,"source":"GHSA-gm7f-v959-fr2g"},{"ecosystem":"Go","fixed":["4.85.0"],"introduced":["0"],"last_affected":[],"package":"github.com/fleetdm/fleet/v4","purl":"pkg:golang/github.com/fleetdm/fleet/v4","source":"GHSA-gm7f-v959-fr2g"},{"ecosystem":"Go","fixed":["4.85.0"],"introduced":["0"],"last_affected":[],"package":"github.com/fleetdm/fleet/v4","purl":"pkg:golang/github.com/fleetdm/fleet/v4","source":"GO-2026-5812"}],"prev":{"headline":"Mastodon: Insufficient verification of email addresses","id":"CVE-2026-41259"},"products":["fleet"],"published":"2026-08-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-26","vendors":["fleetdm"]},"summary":"Authenticated users can read other teams' policy details by bypassing team isolation checks in the global policy read endpoint.","url":"https://insights.sbomify.com/CVE-2026-41262/"}