Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 3.1amended

Fleet: ORDER BY column injection on activity list endpoints

CVE-2026-101046GHSA-rxhg-vcww-2mpw

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/fleetdm/fleet/v4 4.89.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
3.1 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS
  • CVE-2026-101046: 0.17% estimated exploitation activity in the next 30 days; percentile 6.47 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 nodekey 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 nodekey 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 activitypast (e.g. details on /api/v1/fleet/activities, which is not in…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-rxhg-vcww-2mpw

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6269

  3. Revision 1 · created ·

    Published from osv record GHSA-rxhg-vcww-2mpw

Agent brief

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

# Patch Next advisory brief: CVE-2026-101046

Advisory: Fleet: ORDER BY column injection on activity list endpoints
IDs: CVE-2026-101046, GHSA-rxhg-vcww-2mpw
Record: https://patchnext.com/advisories/cve-2026-101046 (revision 3, source checked 26 Oct 2026, 15:28 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.1)
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.89.0. A vendor fix does not mean a deployment is fixed.

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

## 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://osv.dev/vulnerability/GHSA-rxhg-vcww-2mpw (OSV record GHSA-rxhg-vcww-2mpw lists affected ranges: Go github.com/fleetdm/fleet/v4 >=0 <4.89.0 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6269 (OSV record GO-2026-6269 lists affected ranges: Go github.com/fleetdm/fleet/v4 >=0 <4.89.0 (fixed))
- Verified: https://github.com/advisories/GHSA-rxhg-vcww-2mpw (GitHub-reviewed advisory GHSA-rxhg-vcww-2mpw lists affected ranges: Go github.com/fleetdm/fleet/v4 >=0 <4.89.0)

Commands are suggestions: review each one before running it.

Loading voting…