Fleet: Unauthenticated Android device disenrollment vulnerability via Pub/Sub endpoint

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:L · score source

EPSS

• CVE-2026-24004: 0.30% estimated exploitation activity in the next 30 days; percentile 22.53 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

26 Feb 2026, 19:38 UTC

Last modified by the source

10 Mar 2026, 18:22 UTC

Source last checked

26 Oct 2026, 15:15 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-9pm7-6g36-6j78

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-24004

Advisory: Fleet: Unauthenticated Android device disenrollment vulnerability via Pub/Sub endpoint
IDs: CVE-2026-24004, GHSA-9pm7-6g36-6j78
Record: https://patchnext.com/advisories/cve-2026-24004 (revision 1, source checked 26 Oct 2026, 15:15 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/fleetdm/fleet/v4 4.80.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/fleetdm/fleet/v4: affected < 4.80.1; fixed in 4.80.1

## Suggested inspection (read-only)
- Go github.com/fleetdm/fleet/v4: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/fleetdm/fleet/v4.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-9pm7-6g36-6j78 (GitHub-reviewed advisory GHSA-9pm7-6g36-6j78 lists affected ranges: Go github.com/fleetdm/fleet/v4 >=0 <4.80.1)

Commands are suggestions: review each one before running it.