{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-34387 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-34387 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-34387 is a medium-severity command injection vulnerability in fleetdm fleet, published on 27 Mar 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-34387 and fix it if it is affected.\n\nWhat it is: CVE-2026-34387 is a medium-severity command injection vulnerability in fleetdm fleet, published on 27 Mar 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-34387 in the wild and no public exploit code.\n\nAffected product: fleetdm fleet. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-34387/ (Markdown: https://insights.sbomify.com/CVE-2026-34387/index.md)","id":"CVE-2026-34387","markdown":"https://insights.sbomify.com/CVE-2026-34387/index.md","name":"CVE-2026-34387","record":{"aliases":["GHSA-7rhw-5mpv-gp4h"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Device management software","requires_auth":"high_privilege","summary":"Attackers can execute arbitrary code as root or SYSTEM on managed hosts via crafted software package metadata in uninstall scripts.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"fleet","vendor":"fleetdm"}],"cvss":{"score":5.7,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U","version":"4.0"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"Fleet is open source device management software. Prior to 4.81.1, a command injection vulnerability in Fleet's software installer pipeline allows an attacker to achieve arbitrary code execution as root (macOS/Linux) or SYSTEM (Windows) on managed hosts when an uninstall is triggered for a crafted software package. Version 4.81.1 patches the issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Fleet vulnerable to OS command injection via crafted software package metadata in uninstall scripts","id":"CVE-2026-34387","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Fleet vulnerable to Denial of Service via unhandled gRPC log type in launcher endpoint","id":"CVE-2026-34388"},"packages":[],"prev":{"headline":"Fleet vulnerable to SQL injection in MDM bootstrap package by authenticated team or global admin","id":"CVE-2026-34386"},"products":["fleet"],"published":"2026-03-27","related":[{"cvss_score":10,"headline":"SAML authentication vulnerability in Fleet","id":"CVE-2020-26276","kev_date_added":null,"published":"2020-12-17"},{"cvss_score":9.3,"headline":"Fleet before 4.87.0 Authentication Bypass via Device Identifiers","id":"CVE-2026-103264","kev_date_added":null,"published":"2026-10-01"},{"cvss_score":9.3,"headline":"Fleet has a JWT signature bypass vulnerability in Azure AD MDM enrollment","id":"CVE-2026-23518","kev_date_added":null,"published":"2026-01-21"},{"cvss_score":8.7,"headline":"Fleet server may terminate unexpectedly when handling certain gRPC requests","id":"CVE-2026-26062","kev_date_added":null,"published":"2026-05-14"},{"cvss_score":8.7,"headline":"Fleet's unbounded request body read allows remote Denial of Service","id":"CVE-2026-26061","kev_date_added":null,"published":"2026-03-27"},{"cvss_score":8.2,"headline":"Fleet has a Windows MDM management endpoint authentication bypass","id":"CVE-2026-23998","kev_date_added":null,"published":"2026-05-14"},{"cvss_score":8.2,"headline":"Fleet Windows MDM Azure AD JWT Authentication Bypass","id":"CVE-2026-24899","kev_date_added":null,"published":"2026-05-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"total"},"state":"PUBLISHED","updated":"2026-03-27","vendors":["fleetdm"]},"summary":"Attackers can execute arbitrary code as root or SYSTEM on managed hosts via crafted software package metadata in uninstall scripts.","url":"https://insights.sbomify.com/CVE-2026-34387/"}