GHSA-rxhg-vcww-2mpw: Fleet ORDER BY Column Injection On Vulnerability

LOW
CVSS 3.1
CWE-89
Published
Advisory Summary

GHSA-rxhg-vcww-2mpw is a LOW (CVSS 3.1) order by column injection on vulnerability (CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')) affecting Fleet libraries in the Go ecosystem. The issue involves order by column injection on activity list endpoints. Remediation is available by upgrading affected packages to version 4.89.0.

GHSA-rxhg-vcww-2mpw at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-rxhg-vcww-2mpw
Severity LOW
CVSS v3.1 Base Score 3.1
CWE Classification CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Affected Product Fleet
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 3.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix GHSA-rxhg-vcww-2mpw

To remediate this vulnerability, upgrade all affected Fleet dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/fleetdm/fleet/v4 fixed: 4.89.0
Upgrade github.com/fleetdm/fleet/v4 to 4.89.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/fleetdm/fleet/v4

How to Check if You Are Affected

To determine whether your application is affected by GHSA-rxhg-vcww-2mpw, inspect your project dependencies for Fleet:

inspect dependencies for github.com/fleetdm/fleet/v4

Analyze the terminal output to locate any version of Fleet in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.89.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'), where the product constructs all or part of an sql command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended sql command when it is sent to a downstream component. without sufficient removal or quoting of sql syntax in user-controllable inputs, the generated sql query can cause those inputs to be interpreted as sql instead of ordinary user data. In Fleet, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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.

GHSA-rxhg-vcww-2mpw Affected Fleet Versions

1 component(s)
Fixed Versions:
4.89.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/fleetdm/fleet/v4
Go
< 4.89.0
4.89.0

References

Frequently Asked Questions

What is GHSA-rxhg-vcww-2mpw?
GHSA-rxhg-vcww-2mpw is a security vulnerability in Fleet involving ORDER BY column injection on activity list endpoints under CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection').
Which Fleet versions are affected?
Affected versions include releases prior to 4.89.0 across affected packages: github.com/fleetdm/fleet/v4.
What version fixes GHSA-rxhg-vcww-2mpw?
Upgrading to 4.89.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/fleetdm/fleet/v4 affected?
Yes, github.com/fleetdm/fleet/v4 is affected in releases prior to 4.89.0. Upgrade your dependency to 4.89.0 or later.
What is the CVSS score of GHSA-rxhg-vcww-2mpw?
GHSA-rxhg-vcww-2mpw has a CVSS v3.1 base score of 3.1 (LOW) with vector string CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N.
What CWE is associated with GHSA-rxhg-vcww-2mpw?
GHSA-rxhg-vcww-2mpw is classified under CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.).
How can I check Go dependencies for GHSA-rxhg-vcww-2mpw?
Run the dependency tree command: 'inspect dependencies for github.com/fleetdm/fleet/v4'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-rxhg-vcww-2mpw",
  "modified" : "2026-08-20T18:44:36Z",
  "published" : "2026-08-20T18:44:36Z",
  "aliases" : [ ],
  "summary" : "Fleet: ORDER BY column injection on activity list endpoints",
  "details" : "### Summary\n\nAn authenticated user with read access to Activity could influence the `ORDER BY` clause of the activity list endpoints by supplying an arbitrary sort column:\n\n- `GET /api/v1/fleet/activities` (`ListActivities`)\n- `GET /api/v1/fleet/hosts/{id}/activities` (`ListHostPastActivities`)\n\nThis 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.\n\n### Impact\n\nRead-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.\n\n### Remediation\n\nThe 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.\n\n### Affected versions\n\n`< fleet-v4.89.0`. Fixed in `fleet-v4.89.0`.\n\n### Credit\n\nThanks to @axel-corsiez for the report.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/fleetdm/fleet/v4"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "4.89.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/fleetdm/fleet/security/advisories/GHSA-rxhg-vcww-2mpw"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/fleetdm/fleet"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/fleetdm/fleet/releases/tag/fleet-v4.89.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-89" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-20T18:44:36Z",
    "nvd_published_at" : null
  }
}