Summary
Fleet vulnerable to SQL Injection in MDM bootstrap package by authenticated team or global admin
A SQL Injection vulnerability in Fleet's MDM bootstrap package configuration allows an authenticated user with Team Admin or Global Admin privileges to modify arbitrary team configurations, exfiltrate sensitive data from the Fleet database, and inject arbitrary content into team configs via direct API calls.
Workarounds
If an immediate upgrade is not possible, affected Fleet users should temporarily disable Apple MDM or limit admin roles.
For more information
If there are any questions or comments about this advisory:
Send an email to [email protected]
Join #fleet in osquery Slack
Credits
Fleet thanks the Secfox Research Team (@secfox-ai) for responsibly reporting this issue.
Impact
An authenticated user with Team Admin or Global Admin role can exploit a flaw in how user-supplied input is handled during MDM bootstrap package configuration. Insufficient server-side input validation allows crafted input to manipulate database queries in unintended ways.
Successful exploitation could enable cross-team data corruption, exfiltration of sensitive information such as password hashes and API tokens, and potential privilege escalation. Exploitation requires authentication with team or global admin privileges and MDM to be enabled.
This issue does not affect instances where Apple MDM is disabled.
Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-34386? CVE-2026-34386 is a medium-severity SQL injection vulnerability in github.com/fleetdm/fleet/v4 (go), affecting versions < 4.81.0. It is fixed in 4.81.0. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
- Which versions of github.com/fleetdm/fleet/v4 are affected by CVE-2026-34386? github.com/fleetdm/fleet/v4 (go) versions < 4.81.0 is affected.
- Is there a fix for CVE-2026-34386? Yes. CVE-2026-34386 is fixed in 4.81.0. Upgrade to this version or later.
- Is CVE-2026-34386 exploitable, and should I be worried? Whether CVE-2026-34386 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-34386 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-34386? Upgrade
github.com/fleetdm/fleet/v4to 4.81.0 or later.