CVE-2026-24004: Fleet: Unauthenticated Android device disenrollment vulnerability via Pub/Sub endpoint

Published Feb 26, 2026
·
Updated

Summary

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.

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.

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 security@fleetdm.com Join #fleet in osquery Slack

Credits

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

Other sources

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.

MITRE

Affected Software

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

Event History

Feb 26, 2026
CVE Published
via MITRE·02:43 AM
Data Sourced
via MITRE·02:43 AM
DescriptionWeakness
Data Sourced
via NVD·03:16 AM
DescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·07:38 PM
Data Sourced
via GitHub·07:38 PM
DescriptionWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-24004?

CVE-2026-24004 is considered a high-severity vulnerability due to its potential to allow unauthenticated device disenrollment.

2

How do I fix CVE-2026-24004?

To mitigate CVE-2026-24004, upgrade Fleet to version 4.80.1 or later to ensure the vulnerability is patched.

3

What impact does CVE-2026-24004 have on device management?

CVE-2026-24004 can lead to the unauthorized disenrollment of Android devices from Fleet, compromising device management.

4

In which versions of Fleet is CVE-2026-24004 present?

CVE-2026-24004 affects versions of Fleet prior to 4.80.1.

5

Who is affected by CVE-2026-24004?

Organizations using Fleet Android MDM versions below 4.80.1 are impacted by CVE-2026-24004.

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