Skip to main content
VulnerabilityPublished

CVE-2026-24004: fleetdm fleet · Missing Authorization

Affects fleetdm fleetSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 1.7 Low : upgrade to 4.80.1 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
1.7Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.80.1
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N/E:U

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade fleet and fleetdm/fleet to 4.80.1.

Affected software

ProductAffectedFixed in
fleetdmfleetAffected
  • <4.80.1
Fixed in
  • 4.80.1
GitHubfleetdm/fleetpkg:github/fleetdm/fleetOther threatsAffected
  • <4.80.1
Fixed in
  • 4.80.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should upgrade Fleet to version 4.80.1 or later as soon as possible to apply the official fix. If immediate upgrading is not possible, temporarily disabling the Android MDM feature in Fleet will prevent exploitation of this vulnerability. Additionally, monitoring network traffic to the Android MDM Pub/Sub endpoint for unusual or unauthorized requests can help detect exploitation attempts. Implementing network-level access controls to restrict access to Fleet management endpoints to trusted sources can further reduce risk. Regular audits of enrolled devices to detect unexpected unenrollments can aid in early detection of exploitation. Finally, educating security teams about this specific vulnerability ensures timely response and remediation.

Description

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.

References

Community reviews

Loading reviews…