dbcve.org
FleetApplication · Fleetdm

CVE-2026-24004

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-26
Fix available
A fix is available. Upgrade to 4.80.1 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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. In versions prior to 4.80.1, a vulnerability in Fleet’s Android MDM Pub/Sub handling could allow unauthenticated requests to trigger device unenrollment events. This may result in unauthorized removal of individual Android devices from Fleet management. If Android MDM is enabled, an attacker could send a crafted request to the Android Pub/Sub endpoint to unenroll a targeted Android device from Fleet without authentication. This issue does not grant access to Fleet, allow execution of commands, or provide visibility into device data. Impact is limited to disruption of Android device management for the affected device. Version 4.80.1 fixes the issue. If an immediate upgrade is not possible, affected Fleet users should temporarily disable Android MDM.

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

Fleet's Android MDM Pub/Sub endpoint lacks proper authentication validation, allowing unauthenticated attackers to send crafted requests that trigger device unenrollment events. The vulnerability resides in the message handling logic for Android device management operations, where authorization checks are not enforced before processing unenrollment commands.

MitigationUpgrade to Fleet version 4.80.1 to patch the vulnerability. If immediate upgrade is not feasible, temporarily disable Android MDM as a compensating control until the patch can be 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.80.1

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 checks

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

  1. Identify the installed Fleet version
    Run 'fleetctl --version' or check the Fleet UI dashboard version display. If using containerized deployment, check the container image tag or Helm chart version.
    Affected if The installed version is below 4.80.1 (e.g., 4.79.0, 4.78.x, etc.)
  2. Confirm Android MDM is enabled
    Access Fleet UI, navigate to Settings > Mobile Device Management, or use 'fleetctl get mdm' command to check if Android device management features are configured and active.
    Affected if Android MDM enrollment or management features are enabled in the Fleet instance
  3. Inspect Android MDM Pub/Sub endpoint configuration
    Review the Fleet server configuration files or API endpoints related to Android device management message handling. Check if the Pub/Sub webhook or API endpoint for Android unenrollment is exposed and accessible.
    Affected if The Android MDM Pub/Sub endpoint is publicly accessible without additional authentication layers beyond what Fleet provides

You are affected if your Fleet version is below 4.80.1 AND Android MDM functionality is enabled, as the unauthenticated Pub/Sub endpoint can be exploited to trigger device unenrollment.

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.80.1 or later
Fixed in 4.80.1
Interim mitigation

Upgrade to Fleet version 4.80.1 to patch the vulnerability. If immediate upgrade is not feasible, temporarily disable Android MDM as a compensating control until the patch can be applied.

Recommended fix High confidence

Fleet version 4.80.1

  1. Upgrade Fleet to version 4.80.1 or later
  2. After upgrading, verify that Android MDM functionality is working correctly by checking device enrollment status
  3. If immediate upgrade is not possible, temporarily disable Android MDM as a mitigation until upgrade can be performed

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

Fix this in Fleet Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24004 — 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-24004 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