🛡️ CVE-2026-26186 — fleet
Description
Fleet has an SQL Injection vulnerability via backtick escape in ORDER BY parameter
Summary
A SQL Injection vulnerability in Fleet’s software versions API allowed authenticated users to inject arbitrary SQL expressions via the order_key query parameter. Due to unsafe use of goqu.I() when constructing the ORDER BY clause, specially crafted input could escape identifier quoting and be interpreted as executable SQL.
Impact
An authenticated attacker with access to the affected endpoint could inject SQL expressions into the underlying MySQL query. Although the injection occurs in an ORDER BY context, it is sufficient to enable blind SQL injection techniques that can disclose database information through conditional expressions that affect result ordering. Crafted expressions may also cause excessive computation or query failures, potentially leading to degraded performance or denial of service.
No direct evidence of reliable data modification or stacked query execution was demonstrated.
Workarounds
If an immediate upgrade is not possible, users should restrict access to the affected endpoint to trusted roles only and ensure that any user-supplied sort or column parameters are strictly allow-listed at the application or proxy layer.
For more information
If there are any questions or comments about this advisory:
Email fleet at [security@fleetdm.com](mailto:[email protected])
Join #fleet in [osquery Slack](https://join.slack.com/t/osquery/shared_invite/zt-h29zm0gk-s2DBtGUTW4CFel0f0IjTEw)
Credits
We thank @fuzzztf for responsibly reporting this issue.
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity high, availability high.
Weakness class
CVE-2026-26186 is classified as CWE-89: SQL Injection. Untrusted input is concatenated into an SQL statement, letting an attacker change the query and reach data the request should not return.
Affected software
CVE-2026-26186 is recorded against 2 packages.
- fleet (fixed in 4.80.1)
- github.com/fleetdm/fleet/v4
Timeline and source
Published on 26 February 2026 and last revised on 17 June 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.
References
Details
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| fleet | — | 4.80.1 |
| github.com/fleetdm/fleet/v4 | — | — |
References
Similar Threats
- High CVE-2026-23998
- Medium CVE-2026-24000
- High CVE-2026-24899
- High CVE-2026-26062
- Critical CVE-2026-26191
More CVE 2026 advisories
Browse all of CVE 2026 in the advisory index.
Site Security Check
Is fleet part of your stack?
CVE-2026-26186 is rated CVSS 8.8 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.