CVE-2026-46370: Github.com/fleetdm/fleet/v4 Fleet Has Observer-level Enrollment Secret Vulnerability

MODERATE
Advisory Identifier: GHSA-vxm7-9x8v-8gm4
CVSS 6.5
CWE-89 CWE-200
Published
Advisory Summary

CVE-2026-46370 is a MODERATE (CVSS 6.5) fleet has observer-level enrollment secret vulnerability (CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')) affecting Github.com/fleetdm/fleet/v4 libraries in the Go ecosystem. The issue involves fleet has observer-level enrollment secret extraction via order by oracle on labels host-listing endpoint. Remediation is available by upgrading affected packages to version 4.84.2.

CVE-2026-46370 at a Glance

CVE Identifier CVE-2026-46370
GHSA Identifier GHSA-vxm7-9x8v-8gm4
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Affected Product Github.com/fleetdm/fleet/v4
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 6.5

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

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

How to Fix CVE-2026-46370

To remediate this vulnerability, upgrade all affected Github.com/fleetdm/fleet/v4 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.84.2
Upgrade github.com/fleetdm/fleet/v4 to 4.84.2
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 CVE-2026-46370, inspect your project dependencies for Github.com/fleetdm/fleet/v4:

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

Analyze the terminal output to locate any version of Github.com/fleetdm/fleet/v4 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.84.2), 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 Github.com/fleetdm/fleet/v4, 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 A vulnerability in Fleet's labels host-listing endpoint allowed authenticated users with the lowest-privilege Observer role to extract host enrollment secrets (`node_key`, `orbit_node_key`) through a cursor-based binary search oracle. The endpoint accepted a user-supplied `order_key` parameter that was not validated against a column allowlist, permitting sort order to be driven by sensitive columns in a joined table. ### Impact The `GET /api/v1/fleet/labels/{id}/hosts` endpoint constructs its query using a deprecated helper that did not restrict which columns could appear in the `ORDER BY` clause. An attacker with Global Observer or Team Observer credentials could supply a sensitive column name (for example, `h.node_key`) as `order_key` and combine it with the cursor-based `after` parameter to binary-search the values of those columns one character at a time. The targeted values never appeared in the response body, but the presence or absence of results revealed each character. The `node_key` and `orbit_node_key` values are the long-lived shared secrets used by osquery and Orbit agents to authenticate to the Fleet server. An attacker who extracted these keys could: - Impersonate enrolled hosts to Fleet's osquery and Orbit endpoints - Submit fabricated query results and host inventory data - Retrieve pending scripts and MDM commands queued for the host - Poison compliance and policy results across the Fleet deployment Exploitation required authenticated Observer access. Fleet deployments that restrict Observer roles to fully trusted users were at lower practical risk, but the secrets exposed are high-value and long-lived. ### Patches - v4.85.0 ### Workarounds If an immediate upgrade is not possible, administrators should: - Restrict the Observer role to fully trusted users until the patch is applied - Rotate `node_key` and `orbit_node_key` for any host suspected of exposure by re-enrolling the affected hosts ### For more information If there are any questions or comments about this advisory: Email Fleet at [security@fleetdm.com](mailto:security@fleetdm.com) Join #fleet in [osquery Slack](https://join.slack.com/t/osquery/shared_invite/zt-h29zm0gk-s2DBtGUTW4CFel0f0IjTEw) ### Credits Fleet thanks the Security Team at Palantir Technologies for responsibly reporting this issue.

CVE-2026-46370 Affected Github.com/fleetdm/fleet/v4 Versions

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

References

Frequently Asked Questions

What is CVE-2026-46370?
CVE-2026-46370 is a security vulnerability in Github.com/fleetdm/fleet/v4 involving Fleet has observer-level enrollment secret extraction via ORDER BY oracle on labels host-listing endpoint under CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection').
Which Github.com/fleetdm/fleet/v4 versions are affected?
Affected versions include releases prior to 4.84.2 across affected packages: github.com/fleetdm/fleet/v4.
What version fixes CVE-2026-46370?
Upgrading to 4.84.2 (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.84.2. Upgrade your dependency to 4.84.2 or later.
What is the CVSS score of CVE-2026-46370?
CVE-2026-46370 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-46370?
CVE-2026-46370 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 CVE-2026-46370?
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-vxm7-9x8v-8gm4",
  "modified" : "2026-06-26T20:20:29Z",
  "published" : "2026-06-12T21:00:42Z",
  "aliases" : [ "CVE-2026-46370" ],
  "summary" : "Fleet has observer-level enrollment secret extraction via ORDER BY oracle on labels host-listing endpoint",
  "details" : "### Summary\n\nA vulnerability in Fleet's labels host-listing endpoint allowed authenticated users with the lowest-privilege Observer role to extract host enrollment secrets (`node_key`, `orbit_node_key`) through a cursor-based binary search oracle. The endpoint accepted a user-supplied `order_key` parameter that was not validated against a column allowlist, permitting sort order to be driven by sensitive columns in a joined table.\n\n### Impact\n\nThe `GET /api/v1/fleet/labels/{id}/hosts` endpoint constructs its query using a deprecated helper that did not restrict which columns could appear in the `ORDER BY` clause. An attacker with Global Observer or Team Observer credentials could supply a sensitive column name (for example, `h.node_key`) as `order_key` and combine it with the cursor-based `after` parameter to binary-search the values of those columns one character at a time. The targeted values never appeared in the response body, but the presence or absence of results revealed each character.\n\nThe `node_key` and `orbit_node_key` values are the long-lived shared secrets used by osquery and Orbit agents to authenticate to the Fleet server. An attacker who extracted these keys could:\n\n- Impersonate enrolled hosts to Fleet's osquery and Orbit endpoints\n- Submit fabricated query results and host inventory data\n- Retrieve pending scripts and MDM commands queued for the host\n- Poison compliance and policy results across the Fleet deployment\n\nExploitation required authenticated Observer access. Fleet deployments that restrict Observer roles to fully trusted users were at lower practical risk, but the secrets exposed are high-value and long-lived.\n\n### Patches\n\n- v4.85.0\n\n### Workarounds\n\nIf an immediate upgrade is not possible, administrators should:\n\n- Restrict the Observer role to fully trusted users until the patch is applied\n- Rotate `node_key` and `orbit_node_key` for any host suspected of exposure by re-enrolling the affected hosts\n\n### For more information\n\nIf there are any questions or comments about this advisory:\n\nEmail Fleet at [security@fleetdm.com](mailto:security@fleetdm.com)\nJoin #fleet in [osquery Slack](https://join.slack.com/t/osquery/shared_invite/zt-h29zm0gk-s2DBtGUTW4CFel0f0IjTEw)\n\n### Credits\n\nFleet thanks the Security Team at Palantir Technologies for responsibly reporting this issue.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/fleetdm/fleet/v4"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "4.84.2"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 4.84.1"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/fleetdm/fleet/security/advisories/GHSA-vxm7-9x8v-8gm4"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/fleetdm/fleet"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200", "CWE-89" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-12T21:00:42Z",
    "nvd_published_at" : null
  }
}