Fleet: ORDER BY column injection on activity list endpoints
Published 20 Aug 2026 · Updated 28 Sept 2026
Is your project on an affected github.com/fleetdm/fleet/v4?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <4.89.0
- Fixed in
- 4.89.0
go get github.com/fleetdm/fleet/v4@v4.89.0Details
Summary
An authenticated user with read access to Activity could influence the ORDER BY clause of the activity list endpoints by supplying an arbitrary sort column:
GET /api/v1/fleet/activities(ListActivities)GET /api/v1/fleet/hosts/{id}/activities(ListHostPastActivities)
This originated from the deprecated cursor-pagination helper (appendListOptionsWithCursorToSQL), which interpolated the caller-supplied order key into SQL without an allowlist. The original report's node_key extraction scenario (/api/v1/fleet/labels/{id}/hosts) was remediated separately in #44385; these two activity endpoints were the residual call sites, neither of which joins the hosts table, so node_key was never reachable through them.
Impact
Read-only. Because the order key was interpolated, an authenticated user with Activity read could sort by columns not otherwise returned in these responses. The exposure was bounded to columns on activity_past (e.g. details on /api/v1/fleet/activities, which is not in that endpoint's SELECT; host-only activities are already excluded by WHERE host_only = false). There is no privilege escalation, write access, or reachability of node_key or other host-join columns through these endpoints.
Remediation
The deprecated helper was removed from the codebase. Both endpoints now pass the caller-supplied sort column through SanitizeColumn, which strips all characters except [\w-.] and backtick-quotes each identifier segment. This closes the injection vector: separators, whitespace, parentheses, and quotes cannot survive sanitization, so an expression-based ORDER BY oracle is not constructable.
Affected versions
< fleet-v4.89.0. Fixed in fleet-v4.89.0.
Credit
Thanks to @axel-corsiez for the report.
Is GHSA-rxhg-vcww-2mpw in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/fleetdm/fleet/v4, and gives you the command that fixes it.
More advisories for github.com/fleetdm/fleet/v4
- LowCVE-2026-54245Fleet: SQL injection in Okta conditional access endpoint allows host-controlled compromise of the Fleet database in github.com/fleetdm/fleet · 25 Aug 2026
- LowCVE-2026-101047Fleet: Unauthenticated download of in-house iOS app binaries via predictable URLs in github.com/fleetdm/fleet · 25 Aug 2026
- MediumCVE-2026-101047Fleet: Unauthenticated download of in-house iOS app binaries via predictable URLs · 20 Aug 2026
- LowCVE-2026-48786Fleet: Observer-class users can view team enroll secrets and credential-bearing configuration via target search endpoint in github.com/fleetdm/fleet · 18 Aug 2026
- MediumCVE-2026-48786Fleet: Observer-class users can view team enroll secrets and credential-bearing configuration via target search endpoint · 12 Aug 2026
- LowCVE-2026-41262Fleet DM Vulnerable to Cross-Team Policy Data Exposure via Global Policy Read Endpoint in github.com/fleetdm/fleet · 7 Jul 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.