CVE-2026-34385
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFleet 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA second-order SQL injection vulnerability exists in Fleet's Apple MDM profile delivery pipeline. Attackers with valid MDM enrollment certificates can exploit this to access or modify sensitive database contents including user credentials, API tokens, and device enrollment secrets.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 4.81.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Fleet versionRun fleetctl version command or access the Fleet UI footer to determine the installed Fleet versionAffected if The installed version is lower than 4.81.0
-
Verify Apple MDM is enabledReview Fleet configuration settings or check if MDM features are active in the Fleet instanceAffected if Apple MDM is enabled in the Fleet deployment
-
Confirm MDM enrollment certificates existCheck whether MDM enrollment certificates have been uploaded or configured in the Fleet MDM settingsAffected if MDM enrollment certificates are present in the system
-
Review MDM profile activity logsExamine Fleet server logs for MDM profile delivery requests and database query patternsAffected if MDM profile delivery is being used and logged in the environment
A Fleet instance is affected if it is running a version below 4.81.0 with Apple MDM enabled and MDM enrollment certificates configured.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.81.0
Upgrade Fleet to version 4.81.0 or later to patch the SQL injection vulnerability in the MDM profile delivery pipeline.
4.81.0
- Backup the Fleet database and configuration files before starting the upgrade
- Stop the Fleet service
- Upgrade Fleet to version 4.81.0 using your deployment method (e.g., package manager, Docker, Kubernetes)
- Start the Fleet service
- Verify the upgrade was successful by checking the Fleet version
- Confirm the Apple MDM profile delivery pipeline is functioning correctly
- Review Fleet logs for any errors or unusual activity
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34385 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34385 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data