Summary
Fleet: Unauthenticated Android device disenrollment vulnerability via Pub/Sub endpoint
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.
Workarounds
If an immediate upgrade is not possible, affected Fleet users should temporarily disable Android MDM.
For more information
If there any questions or comments about this advisory:
Email Fleet at [email protected]
Join #fleet in osquery Slack
Credits
Fleet thanks @secfox-ai for responsibly reporting this issue.
Impact
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.
A critical operation is accessible without requiring any authentication. Typical impact: any user can invoke the privileged function.
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-24004? CVE-2026-24004 is a medium-severity missing authentication for critical function vulnerability in github.com/fleetdm/fleet/v4 (go), affecting versions < 4.80.1. It is fixed in 4.80.1. A critical operation is accessible without requiring any authentication.
- Which versions of github.com/fleetdm/fleet/v4 are affected by CVE-2026-24004? github.com/fleetdm/fleet/v4 (go) versions < 4.80.1 is affected.
- Is there a fix for CVE-2026-24004? Yes. CVE-2026-24004 is fixed in 4.80.1. Upgrade to this version or later.
- Is CVE-2026-24004 exploitable, and should I be worried? Whether CVE-2026-24004 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-24004 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-24004? Upgrade
github.com/fleetdm/fleet/v4to 4.80.1 or later.