CVE-2026-26186: Fleet has a SQL injection via backtick escape in ORDER BY parameter

Published Feb 26, 2026
·
Updated

Summary

A SQL Injection vulnerability in Fleet’s software versions API allowed authenticated users to inject arbitrary SQL expressions via the orderkey 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 Join #fleet in osquery Slack

Credits

We thank @fuzzztf for responsibly reporting this issue.

Other sources

Fleet is open source device management software. A SQL injection vulnerability in versions prior to 4.80.1 allowed authenticated users to inject arbitrary SQL expressions via the orderkey 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. 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. Version 4.80.1 fixes the issue. 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.

NVD

Affected Software

3 affected componentsFixes available
open_source/fleet<4.80.1
go/github.com/fleetdm/fleet/v4<4.80.1
4.80.1
fleetdm fleet<4.80.1

Event History

Feb 26, 2026
CVE Published
via MITRE·12:05 AM
Data Sourced
via MITRE·12:05 AM
DescriptionWeakness
Data Sourced
via NVD·12:16 AM
DescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·03:14 PM
Data Sourced
via GitHub·03:14 PM
DescriptionWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-26186?

CVE-2026-26186 is classified as a critical SQL injection vulnerability.

2

How do I fix CVE-2026-26186?

To remediate CVE-2026-26186, upgrade to Fleet version 4.80.1 or later.

3

Who is affected by CVE-2026-26186?

CVE-2026-26186 affects authenticated users of Fleet versions prior to 4.80.1.

4

What type of vulnerability is CVE-2026-26186?

CVE-2026-26186 is a SQL injection vulnerability that exploits the ORDER BY parameter.

5

Can CVE-2026-26186 lead to data exposure?

Yes, CVE-2026-26186 can allow attackers to execute arbitrary SQL queries, potentially leading to data exposure.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203