dbcve.org
FleetApplication · Fleetdm

CVE-2026-34386

HIGH · 8.8 CVSS v3.1 Published 2026-03-27
Fix available
A fix is available. Upgrade to 4.81.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Fleet is open source device management software. Prior to 4.81.0, 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. 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 confidence

SQL injection in Fleet's MDM bootstrap package configuration API allows authenticated Team Admin or Global Admin users to modify arbitrary team configurations, exfiltrate sensitive data from the database, and inject arbitrary content via direct API calls.

MitigationUpgrade Fleet to version 4.81.0 or later to patch the SQL injection vulnerability. This is a privileged SQL injection requiring admin access, so ensure admin accounts are reviewed and monitor for suspicious API activity until the patch is applied.

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
FleetApplication
Affected:< 4.81.0

CVSS 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
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Fleet version is vulnerable
    Check the installed Fleet version via `fleetctl --version` or the Fleet UI dashboard. Compare against the affected range: versions < 4.81.0 are vulnerable.
    Affected if Installed Fleet version is below 4.81.0
  2. Confirm MDM is enabled
    Check if Fleet's MDM (Mobile Device Management) feature is enabled in the instance. This can be verified in Fleet settings or via `fleetctl get mdm` command if available.
    Affected if MDM functionality is enabled and configured in the Fleet instance
  3. Identify admin users with API access
    Review user roles in Fleet to determine if any Team Admin or Global Admin users exist who would have access to the MDM bootstrap package configuration API endpoint.
    Affected if One or more Team Admin or Global Admin users exist with API access credentials
  4. Review API request logs for MDM endpoints
    Examine Fleet's API audit logs or server access logs for requests to the MDM bootstrap package configuration API endpoint. Look for unusual or suspicious patterns in API calls.
    Affected if API requests to MDM bootstrap configuration endpoint show anomalous patterns or unauthorized modifications

Environment is affected if running Fleet version below 4.81.0 with MDM enabled and having admin accounts capable of accessing the vulnerable bootstrap package configuration API.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.81.0 or later
Fixed in 4.81.0
Interim mitigation

Upgrade Fleet to version 4.81.0 or later to patch the SQL injection vulnerability. This is a privileged SQL injection requiring admin access, so ensure admin accounts are reviewed and monitor for suspicious API activity until the patch is applied.

Recommended fix High confidence

4.81.0

  1. Upgrade Fleet to version 4.81.0 or later
  2. After upgrading, verify that the MDM bootstrap package configuration no longer accepts malicious SQL input
  3. Review Team Admin and Global Admin user permissions to ensure only necessary users have these elevated privileges

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fleet Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34386 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34386 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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