# CVE-2026-46370: Fleet has observer-level enrollment secret extraction via ORDER BY oracle on labels host-listing endpoint

> An observer can extract host enrollment secrets via an ORDER BY oracle, enabling host impersonation and data poisoning in Fleet deployments.

- **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:** 29 Aug 2026
- **Also known as:** GHSA-vxm7-9x8v-8gm4, GO-2026-5682

## What is CVE-2026-46370?

CVE-2026-46370 is a medium-severity 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 labels host-listing endpoint (GET /api/v1/fleet/labels/{id}/hosts) allowed an authenticated user with the lowest-privilege Observer role to extract host enrollment secrets through a sort-order oracle. The endpoint accepted a user-supplied order_key parameter that was not validated against a column allowlist, so an attacker with Global or Team Observer access could set the sort column to a sensitive field such as h.node_key and combine it with the cursor-based after parameter to binary-search the value one character at a time; the targeted value never appeared in the response, but the presence or absence of results revealed each character. Because node_key and orbit_node_key are the long-lived shared secrets that osquery and Orbit agents use to authenticate to the Fleet server, an attacker who reconstructed them could impersonate enrolled hosts, submit fabricated query results and inventory, retrieve pending scripts and MDM commands, and poison compliance and policy results across the deployment. 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-46370?

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-46370?

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

## Is CVE-2026-46370 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46370 is a medium-severity 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-46370 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-46370/ (Markdown: https://insights.sbomify.com/CVE-2026-46370/index.md)
```

## Sources

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

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