Fleet versions before 4.83.0 have a denial of service vulnerability due to improper handling of gzip-compressed request bodies. Unauthenticated attackers can send small, highly compressed requests to unauthenticated endpoints, which expand during decompression and exhaust server memory, causing the Fleet instance to crash.
Fleet versions prior to 4.89.0 have an unbounded recursion vulnerability in the Apple MDM enrollment property list parsing. This flaw allows unauthenticated attackers to send a crafted binary plist payload that triggers exponential resource consumption, causing the server to crash. The vulnerability can be exploited by sending a payload of about 150 bytes to the enrollment endpoints, leading to CPU and memory exhaustion.
Fleet versions before 4.89.0 fail to properly filter MDM command results by team authorization in the commands/results endpoint. Team-scoped users can read MDM command results for hosts on other teams when a shared command UUID targets hosts across multiple teams, exposing host UUIDs, command payloads, and device responses.
Fleet versions before 4.87.0 contain an authentication bypass vulnerability in the device API that accepts hostnames and hardware serials as authentication tokens in addition to device UUIDs. Unauthenticated attackers who know or guess these non-secret identifiers can authenticate as iOS/iPadOS hosts to read device data and trigger device-scoped actions including software installation and MDM migration.
Fleet versions before 4.87.0 have a vulnerability where two endpoints serving in-house iOS application packages and manifests are not protected by the intended random, time-limited URL token. This allows unauthenticated attackers with network access to the Fleet server to download in-house IPA binaries and metadata by guessing sequential title identifiers. The issue affects only the enterprise tier and does not impact the free tier. The vulnerability results in read-only information disclosure without privilege escalation or write access.
Fleet before 4.89.0 contains an SQL injection vulnerability in the activity list endpoints (GET /api/v1/fleet/activities and GET /api/v1/fleet/hosts/{id}/activities). The deprecated cursor-pagination helper appendListOptionsWithCursorToSQL interpolated the caller-supplied sort/order key into the SQL ORDER BY clause without an allowlist, so an authenticated user with read access to Activity could order results by arbitrary columns. The impact is read-only and bounded to columns on the activity_past table that are not otherwise returned in these responses (e.g. details), allowing their values to be inferred through the resulting sort order; there is no write access, privilege escalation, or reachability of node_key or other host-join columns through these endpoints. Fixed in 4.89.0, which removes the deprecated helper and passes the sort column through SanitizeColumn.
CVE-2026-101045 is an OS command injection vulnerability in fleetdm's fleet product affecting macOS app install and uninstall scripts generated from Homebrew cask metadata before 2026-08-19. The vulnerability arises because some shell metacharacters in the metadata were not properly escaped, allowing crafted metadata to execute arbitrary commands as root on managed macOS hosts. Exploitation requires the malicious metadata to pass both upstream Homebrew cask review and Fleet's automated ingestion review. The issue was fixed in Fleet v4.92.0 with a patch applied centrally on 2026-08-19, which escapes all interpolation sites in the generated manifests. This fix was distributed to all deployments with no customer action required.
Fleet versions prior to 4.86.2 with Fleet Premium and Okta conditional access integration enabled are vulnerable to SQL injection. The vulnerability arises from improper parameterization of a host-supplied value used in a database query. An attacker controlling a single enrolled host can exploit this to read or modify arbitrary data in the Fleet database, potentially extracting session tokens and gaining global administrator access. This access can lead to remote code execution on enrolled hosts. The vulnerability does not affect Fleet instances without the Okta conditional access integration configured. The issue is fixed in version 4.86.2.
CVE-2026-46370 is a SQL injection vulnerability in Fleet, an open-source device management platform built on osquery. Versions up to and including 4.84.1 have a flaw in the labels host-listing endpoint that allows authenticated users with Observer role privileges to extract sensitive host enrollment secrets. The vulnerability arises from improper validation of the order_key parameter, enabling attackers to perform a sort-order oracle attack to reconstruct long-lived shared secrets used for host authentication. This could allow impersonation of enrolled hosts and manipulation of query results and policies. The issue is fixed in version 4.84.2.
Fleet is open source device management software. Prior to version 4.80.1, a vulnerability in Fleet's IP extraction logic allows unauthenticated attackers to bypass API rate limiting by spoofing client IP headers. This may allow brute-force login attempts or other abuse against Fleet instances exposed to the public internet. Fleet extracted client IP addresses from request headers (`True-Client-IP`, `X-Real-IP`, `X-Forwarded-For`) without validating that those headers originate from a trusted proxy. The extracted IP is used as the key for rate limiting and IP ban decisions. As a result, an attacker could rotate the value of these headers on each request, causing Fleet to treat each attempt as coming from a different client. This effectively bypasses per-IP rate limits on sensitive endpoints such as the login API, enabling unrestricted brute-force or credential stuffing attacks. This issue primarily affects Fleet instances that are directly exposed to the internet without a reverse proxy that overwrites forwarded-IP headers. Instances behind a properly configured proxy or WAF are less affected. Version 4.80.1 contains a patch. If an immediate upgrade is not possible, administrators should ensure Fleet is deployed behind a reverse proxy (e.g., nginx, Cloudflare, AWS ALB) that overwrites `X-Forwarded-For` with the true client IP, and apply rate limiting at the proxy or WAF layer.
Fleet is open source device management software. Prior to version 4.81.0, a vulnerability in Fleet's software installer pipeline could allow a crafted software package to execute arbitrary commands as root (macOS/Linux) or SYSTEM (Windows) on managed endpoints when an uninstall is triggered. When a software package (.pkg, .deb, .rpm, .exe, or .msi) is uploaded to Fleet, metadata is extracted from the package binary and used to generate uninstall scripts. In affected versions, this metadata is not properly sanitized before being included in the generated scripts. A specially crafted package containing malicious values in its metadata fields could result in unintended command execution when the uninstall script runs on managed endpoints. Version 4.81.0 contains a patch. If an immediate upgrade is not possible, administrators should avoid uploading software packages obtained from untrusted or unverified sources. Additionally, administrators can manually inspect and edit auto-generated uninstall scripts before deployment.
Fleet is open source device management software. Prior to version 4.81.0, Fleet contained a denial-of-service (DoS) issue in the gRPC Launcher `PublishLogs` endpoint. In affected versions, certain unexpected input values were not handled gracefully, which could cause the Fleet server process to terminate while processing an authenticated request from an enrolled Launcher host. An authenticated attacker with access to any enrolled Launcher node key could cause an immediate and complete denial of service by sending a single gRPC request to the `PublishLogs` endpoint. This vulnerability impacts availability only. There is no exposure of sensitive data, no authentication bypass, no privilege escalation, and no integrity impact. Version 4.81.0 contains a patch. If upgrading immediately is not possible, the following mitigations can reduce exposure. Restrict network access to the Fleet gRPC endpoint where feasible (for example, limiting inbound access to known host IP ranges); deploy Fleet behind infrastructure that terminates or filters gRPC traffic if Launcher log ingestion is not required; and/or monitor for repeated Fleet process crashes or unexpected restarts indicating potential exploitation.
Fleet versions prior to 4.82.0 have an authentication bypass vulnerability in the Windows MDM enrollment flow. The software accepts Azure AD tokens from any tenant because it validates JWT signatures using Microsoft's multi-tenant JWKS endpoint but does not enforce audience or issuer claims. This flaw allows attackers with access to any Azure AD tenant to use valid Microsoft-signed tokens to enroll unauthorized devices and interact with Fleet's MDM APIs. Sensitive enrollment secrets may be exposed during device management. Version 4.82.0 includes a patch that addresses this issue. Users unable to upgrade immediately should disable Windows MDM as a temporary mitigation.
Fleet is open source device management software. Prior to version 4.80.1, Fleet trusted client-supplied IP address headers when determining the source IP for incoming requests. This allowed authenticated and unauthenticated clients to spoof their apparent IP address and bypass per-IP rate limiting controls. Fleet determines a client’s public IP address using HTTP headers such as X-Forwarded-For, X-Real-IP, and/or True-Client-IP. These headers were trusted without validation. An attacker could supply arbitrary values in these headers, causing Fleet to treat each request as originating from a different IP address. This could allow an attacker to bypass per-IP rate limits and increase the effectiveness of brute-force or password-spraying attempts against authentication endpoints. This issue does not allow authentication bypass, privilege escalation, data exposure, or remote code execution on its own. Version 4.80.1 contains a patch. As a workaround, run Fleet behind a trusted reverse proxy or load balancer that overwrites client IP headers.
Fleet is open source device management software. Prior to version 4.81.0, a vulnerability in Fleet’s Windows MDM management endpoint could allow requests to be processed without proper client certificate validation. In certain circumstances, this could allow an attacker to impersonate an enrolled Windows device and retrieve sensitive configuration data. Fleet’s Windows MDM management endpoint relies on mutual TLS (mTLS) client certificates to authenticate enrolled devices. In affected versions, requests that did not present a client certificate could be incorrectly treated as trusted. As a result, an attacker with prior knowledge of a valid enrolled device identifier could potentially impersonate that device and receive configuration payloads intended for it. These payloads may contain sensitive information such as Wi-Fi or VPN configuration data, certificates, or other secrets delivered through MDM profiles. This issue does not allow enrollment of new devices, administrative access to Fleet, or compromise of the Fleet control plane. Impact is limited to the targeted Windows device. Version 4.81.0 contains a patch. If an immediate upgrade is not possible, affected Fleet users should temporarily disable Windows MDM.
CVE-2026-27806 is an OS command injection vulnerability in the Fleet open source device management software prior to version 4.81.1. It arises from improper handling of a local user's password in the Orbit agent's FileVault disk encryption key rotation flow. The password is interpolated directly into a Tcl/expect script, allowing a specially crafted password containing the '}' character to inject arbitrary Tcl commands. Because the Orbit agent runs with root privileges, this vulnerability allows local unprivileged users to escalate privileges to root. The issue is fixed in Fleet version 4.81.1.
Fleet is open source device management software. Prior to 4.81.1, a vulnerability in Fleet's Windows MDM command processing allows a malicious enrolled device to access MDM commands intended for other devices, potentially exposing sensitive configuration data such as WiFi credentials, VPN secrets, and certificate payloads across the entire Windows fleet. Version 4.81.1 patches the issue.
Fleet is open source device management software. Prior to 4.81.0, Fleet contained an issue in the user invitation flow where the email address provided during invite acceptance was not validated against the email address associated with the invite. An attacker who obtained a valid invite token could create an account under an arbitrary email address while inheriting the role granted by the invite, including global admin. Version 4.81.0 patches the issue.
Fleet is open source device management software. Prior to 4.81.0, a denial-of-service vulnerability in Fleet's gRPC Launcher endpoint allows an authenticated host to crash the entire Fleet server process by sending an unexpected log type value. The server terminates immediately, disrupting all connected hosts, MDM enrollments, and API consumers. Version 4.81.0 patches the issue.
Fleet is open source device management software. Prior to 4.81.1, a command injection vulnerability in Fleet's software installer pipeline allows an attacker to achieve arbitrary code execution as root (macOS/Linux) or SYSTEM (Windows) on managed hosts when an uninstall is triggered for a crafted software package. Version 4.81.1 patches the issue.