Is CVE-2026-46370 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-46370 being exploited in the wild.

How severe is CVE-2026-46370?

Medium severity, with a CVSS score of 6.5, published 26 August 2026.

Which products and versions are affected?

github.com/fleetdm/fleet/v4 (Go) <= 4.84.1, SEMVER:introduced=0,fixed=4.84.2.

Is there a fix for CVE-2026-46370?

Yes. github.com/fleetdm/fleet/v4 (Go): upgrade to 4.84.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-46370 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-46370?

Check whether you run github.com/fleetdm/fleet/v4 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-46370: Fleet SQL injection in labels host-listing endpoint

Q: Is there a fix for CVE-2026-46370?

Yes. github.com/fleetdm/fleet/v4 (Go): upgrade to 4.84.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-46370 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-46370?

Check whether you run github.com/fleetdm/fleet/v4 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-46370 · Severity: medium · CVSS 6.5 · Published 2026-08-26

A vulnerability in Fleet, a device management platform, allows users with low-level 'Observer' permissions to extract sensitive host enrollment secrets. By exploiting a flaw in how the system lists hosts, an attacker can obtain the keys used by devices to authenticate with the management server. This could allow an attacker to impersonate managed computers, submit fake security data, or intercept commands intended for those devices.

Technologies: github.com/fleetdm/fleet/v4 (Go). Vendors: Go.

Quick answers

Is CVE-2026-46370 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-46370 being exploited in the wild.
How severe is CVE-2026-46370?: Medium severity, with a CVSS score of 6.5, published 26 August 2026.
Which products and versions are affected?: github.com/fleetdm/fleet/v4 (Go) <= 4.84.1, SEMVER:introduced=0,fixed=4.84.2.
Is there a fix for CVE-2026-46370?: Yes. github.com/fleetdm/fleet/v4 (Go): upgrade to 4.84.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-46370 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-46370?: Check whether you run github.com/fleetdm/fleet/v4 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/fleetdm/fleet/v4 (Go): upgrade to 4.84.2 or later
```
go get github.com/fleetdm/fleet/v4@v4.84.2
```

Technical details

A blind SQL injection vulnerability exists in the 'GET /api/v1/fleet/labels/{id}/hosts' endpoint due to improper validation of the 'order_key' parameter. The endpoint uses a deprecated helper that fails to restrict the columns used in the ORDER BY clause, allowing an attacker to specify sensitive columns like 'node_key'. By combining this with the cursor-based 'after' parameter, an authenticated Observer can perform a binary search oracle to extract long-lived enrollment secrets character-by-character. These secrets (node_key and orbit_node_key) can be used to impersonate hosts, retrieve MDM commands, or poison inventory data. The issue is fixed in version 4.85.0 (and 4.84.2 according to some advisory metadata).

Affected products

Fleet Device Management (fleetdm) Fleet <= 4.84.1

Identifiers

CVE-2026-46370
GHSA-vxm7-9x8v-8gm4
GO-2026-5682

Timeline

2026-06-11: disclosed
2026-06-11: advisory
2026-06-12: patched: Version 4.85.0 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.