{"answers":{"affected":"3 open source packages ship an affected version, including github.com/fleetdm/fleet/v4.","exploited":"There is no known exploitation of CVE-2026-48786 in the wild and no public exploit code.","fix":"Upgrade github.com/fleetdm/fleet/v4 to 4.87.0 or later.","what":"CVE-2026-48786 is a medium-severity 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-48786 and fix it if it is affected.\n\nWhat it is: CVE-2026-48786 is a medium-severity 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: There is no known exploitation of CVE-2026-48786 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/fleetdm/fleet/v4 (Go): affected all versions; fixed in 4.87.0\n- github.com/fleetdm/fleet/v4 (Go): affected all versions; fixed in 4.87.0\n- github.com/fleetdm/fleet/v4 (Go): affected all versions; fixed in 4.87.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-48786/ (Markdown: https://insights.sbomify.com/CVE-2026-48786/index.md)","id":"CVE-2026-48786","markdown":"https://insights.sbomify.com/CVE-2026-48786/index.md","name":"CVE-2026-48786","record":{"aliases":["GHSA-88p2-jj8w-j8qg","GO-2026-6220"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Fleet device management","requires_auth":"low_privilege","summary":"Low-privilege users can view sensitive team enroll secrets and credentials via the target search endpoint, enabling unauthorized host enrollment and credential theft.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Fleet is an open-source device management platform built on osquery. In versions prior to 4.87.0, the target search endpoint (POST /api/latest/fleet/targets) returned unmasked team enroll secrets and full team configuration, including credential-bearing agent options, to low-privilege observer-class users. Other team-facing endpoints mask these fields for observers, but the target search endpoint did not apply the same sanitization, so an authenticated user with the Observer, Observer+, or Technician role, whether global or team-scoped, could retrieve the secrets and agent options by performing a target search against an observer-runnable query. With a leaked team enroll secret an attacker could enroll unauthorized hosts into the affected team, and if the team's agent options contained credentials such as AWS secret access keys or proxy passwords, those values were disclosed as well. This issue is fixed in version 4.87.0.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Fleet: Observer-class users can view team enroll secrets and credential-bearing configuration via target search endpoint","id":"CVE-2026-48786","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"gin-vue-admin vulnerable to RCE","id":"CVE-2026-48787"},"packages":[{"ecosystem":"Go","fixed":["4.87.0"],"introduced":["0"],"last_affected":[],"package":"github.com/fleetdm/fleet/v4","purl":null,"source":"GHSA-88p2-jj8w-j8qg"},{"ecosystem":"Go","fixed":["4.87.0"],"introduced":["0"],"last_affected":[],"package":"github.com/fleetdm/fleet/v4","purl":"pkg:golang/github.com/fleetdm/fleet/v4","source":"GHSA-88p2-jj8w-j8qg"},{"ecosystem":"Go","fixed":["4.87.0"],"introduced":["0"],"last_affected":[],"package":"github.com/fleetdm/fleet/v4","purl":"pkg:golang/github.com/fleetdm/fleet/v4","source":"GO-2026-6220"}],"prev":{"headline":"Apptainer: Incorrect path matching for 'limit container paths' directive","id":"CVE-2026-48785"},"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-26","vendors":["fleetdm"]},"summary":"Low-privilege users can view sensitive team enroll secrets and credentials via the target search endpoint, enabling unauthorized host enrollment and credential theft.","url":"https://insights.sbomify.com/CVE-2026-48786/"}