# CVE-2026-46371: Fleet: Observer-level enrollment secret extraction via ORDER BY oracle on Apple MDM commands endpoint

> An attacker with Observer role can extract enrollment secrets via SQL injection in the MDM commands endpoint, enabling host impersonation and data access.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-x4qr-qw6h-wvxq, GO-2026-5739

## What is CVE-2026-46371?

CVE-2026-46371 is a medium-severity SQL injection vulnerability in fleetdm fleet, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Fleet is an open-source device management platform built on osquery. In versions up to and including 4.84.1, the Apple MDM commands listing endpoint (GET /api/v1/fleet/mdm/apple/commands) allowed an authenticated user with the lowest-privilege Observer role to extract sensitive values from joined database tables, including host enrollment secrets and Apple Push Notification Service tokens, through a sort-order oracle. The endpoint accepted a user-supplied order_key parameter that was not validated against a column allowlist, and because the underlying query joins the hosts and nano_enrollments tables, an attacker could set the sort column to a sensitive field and combine it with the cursor-based after parameter to binary-search the value one character at a time, with the presence or absence of results revealing each character even though the value never appeared in the response. With extracted node_key or orbit_node_key values an attacker could impersonate enrolled hosts to Fleet's osquery and Orbit endpoints, submit fabricated host data, and retrieve pending scripts and commands. This issue is fixed in version 4.84.2.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-46371?

3 open source packages ship an affected version, including github.com/fleetdm/fleet/v4.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/fleetdm/fleet/v4` | Go | All versions | 4.84.2 |
| `github.com/fleetdm/fleet/v4` | Go | All versions | 4.84.2 |
| `github.com/fleetdm/fleet/v4` | Go | All versions | 4.84.2 |

## How do I fix CVE-2026-46371?

Upgrade github.com/fleetdm/fleet/v4 to 4.84.2 or later.

## Is CVE-2026-46371 being exploited?

There is no known exploitation of CVE-2026-46371 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46371 and fix it if it is affected.

What it is: CVE-2026-46371 is a medium-severity SQL injection vulnerability in fleetdm fleet, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-46371 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/fleetdm/fleet/v4 (Go): affected all versions; fixed in 4.84.2
- github.com/fleetdm/fleet/v4 (Go): affected all versions; fixed in 4.84.2
- github.com/fleetdm/fleet/v4 (Go): affected all versions; fixed in 4.84.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46371/ (Markdown: https://insights.sbomify.com/CVE-2026-46371/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46371
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46371
- OSV: https://osv.dev/vulnerability/CVE-2026-46371

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46371/
Summaries are generated and may contain mistakes; the official description above is the record.