CVE-2026-34385: Fleet's Apple MDM profile delivery has second-order SQL injection that can compromise the database

Published Mar 27, 2026
·
Updated

Summary

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.

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.

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 security@fleetdm.com

Join #fleet in [osquery Slack](https://join.slack.com/t/osquery/sharedinvite/zt-h29zm0gk-s2DBtGUTW4CFel0f0IjTEw)

Credits

Fleet thanks@secfox-ai for responsibly reporting this issue.

Other sources

Fleet is open source device management software. Prior to 4.81.0, a 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. Version 4.81.0 patches the issue.

MITRE

Affected Software

3 affected componentsFixes available
fleetdm fleet<4.81.0
go/github.com/fleetdm/fleet/v4<4.81.0
4.81.0
fleetdm fleet<4.81.0

Event History

Mar 27, 2026
CVE Published
via MITRE·06:29 PM
Data Sourced
via MITRE·06:29 PM
DescriptionWeakness
Data Sourced
via NVD·07:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:16 PM
Affected Software
Mar 30, 2026
Advisory Published
via GitHub·07:17 PM
Data Sourced
via GitHub·07:17 PM
DescriptionWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-34385?

CVE-2026-34385 is classified as a critical vulnerability due to its potential for severe exploitation through SQL injection.

2

How do I fix CVE-2026-34385?

To fix CVE-2026-34385, users should upgrade Fleet to version 4.81.0 or later.

3

Who is affected by CVE-2026-34385?

CVE-2026-34385 affects users of Fleet's Apple MDM profile delivery before version 4.81.0.

4

What type of attack does CVE-2026-34385 facilitate?

CVE-2026-34385 facilitates a second-order SQL injection attack that can compromise the database.

5

Can an attacker exploit CVE-2026-34385 without a valid MDM certificate?

No, an attacker requires a valid MDM enrollment certificate to exploit CVE-2026-34385.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203