Summary
Fleet's Apple MDM profile delivery has second-order SQL Injection that can compromise the database
A critical second-order SQL Injection vulnerability in Fleet's Apple MDM profile delivery pipeline could allow an attacker with a valid MDM enrollment certificate to exfiltrate or modify the contents of the Fleet database, including user credentials, API tokens, and device enrollment secrets.
Workarounds
If an immediate upgrade is not possible, affected Fleet users should temporarily disable Apple MDM.
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@secfox-ai for responsibly reporting this issue.
Impact
If Apple MDM is enabled, an attacker controlling an enrolled device can send a malicious UDID during the MDM Authenticate check-in. The UDID is stored safely via parameterized queries, but is later interpolated directly into SQL when the async worker processes the job. This enables blind, boolean-based, and UNION-based SQL injection across four simultaneous subqueries.
Because Fleet's database driver is configured with multiStatements=true, the attacker can also execute stacked queries, enabling arbitrary writes to the database. This includes inserting new admin accounts, modifying configuration, deploying malicious profiles or scripts to managed devices, and deleting data.
Exploitation requires a valid SCEP-issued enrollment certificate (mTLS), but any enrolled device, including attacker-controlled devices, can exploit this vulnerability.
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-34385? CVE-2026-34385 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-34385? github.com/fleetdm/fleet/v4 (go) versions < 4.81.0 is affected.
- Is there a fix for CVE-2026-34385? Yes. CVE-2026-34385 is fixed in 4.81.0. Upgrade to this version or later.
- Is CVE-2026-34385 exploitable, and should I be worried? Whether CVE-2026-34385 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-34385 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-34385? Upgrade
github.com/fleetdm/fleet/v4to 4.81.0 or later.