CVE-2026-26186

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 77% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

February 26, 2026

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Aug 2, 2026
Patch available. Sources: github.
github Patch Available

SQL injection via backtick escape in ORDER BY parameter · Advisory · fleetdm/fleet · GitHub

https://github.com/fleetdm/fleet/security/advisories/GHSA-49xw-vfc4-7p43

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/fleetdm/fleet/v44.80.1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 13:02 UTCOSV refresh
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 19:27 UTCEPSS rescore
  4. 2026-09-16 14:07 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-13 16:47 UTCEPSS rescore
  7. 2026-09-12 15:01 UTCEPSS rescore
  8. 2026-09-11 14:52 UTCEPSS rescore
  9. 2026-09-10 09:34 UTCEPSS rescore
  10. 2026-09-08 22:00 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-04 05:06 UTCEPSS rescore
  14. 2026-09-02 14:11 UTCEPSS rescore
  15. 2026-09-01 13:53 UTCEPSS rescore
  16. 2026-09-01 04:39 UTCEPSS rescore
  17. 2026-08-31 16:34 UTCOSV refresh
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-28 21:41 UTCEPSS rescore
  21. 2026-08-27 14:25 UTCEPSS rescore
  22. 2026-08-26 14:46 UTCEPSS rescore
  23. 2026-08-25 13:48 UTCEPSS rescore
  24. 2026-08-23 00:19 UTCEPSS rescore
  25. 2026-08-21 23:49 UTCEPSS rescore
Show 33 more
  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-19 17:03 UTCEPSS rescore
  3. 2026-08-18 13:48 UTCEPSS rescore
  4. 2026-08-17 13:47 UTCEPSS rescore
  5. 2026-08-16 14:56 UTCEPSS rescore
  6. 2026-08-16 02:14 UTCEPSS rescore
  7. 2026-08-15 01:30 UTCEPSS rescore
  8. 2026-08-14 08:58 UTCEG score recompute
  9. 2026-08-13 22:00 UTCEPSS rescore
  10. 2026-08-13 00:58 UTCEG score recompute
  11. 2026-08-12 13:50 UTCEPSS rescore
  12. 2026-08-11 23:54 UTCEG score recompute
  13. 2026-08-11 13:42 UTCEPSS rescore
  14. 2026-08-11 06:17 UTCEG score recompute
  15. 2026-08-11 00:00 UTCEPSS rescore
  16. 2026-08-09 20:45 UTCEG score recompute
  17. 2026-08-09 13:46 UTCEPSS rescore
  18. 2026-08-09 08:36 UTCEG score recompute
  19. 2026-08-08 16:37 UTCEPSS rescore
  20. 2026-08-07 20:39 UTCEG score recompute
  21. 2026-08-06 13:46 UTCEPSS rescore
  22. 2026-08-06 02:59 UTCEG score recompute
  23. 2026-08-05 19:17 UTCEPSS rescore
  24. 2026-08-04 15:10 UTCEPSS rescore
  25. 2026-08-04 05:48 UTCEG score recompute
  26. 2026-08-03 10:36 UTCEPSS rescore
  27. 2026-08-02 19:31 UTCEG score recompute
  28. 2026-08-02 02:26 UTCEPSS rescore
  29. 2026-08-01 04:16 UTCEPSS rescore
  30. 2026-07-30 16:27 UTCEPSS rescore
  31. 2026-07-30 01:30 UTCEPSS rescore
  32. 2026-07-28 15:36 UTCEPSS rescore
  33. 2026-07-27 13:34 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-26186?
CVE-2026-26186 is a high vulnerability published on February 26, 2026. 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 order_key query parameter. Due to unsafe use of goqu.I() when constructing the ORDER BY clause, specially crafted input…
When was CVE-2026-26186 disclosed?
CVE-2026-26186 was first published in the National Vulnerability Database on February 26, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-26186 actively exploited?
CVE-2026-26186 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 77.0% of all scored CVEs.
What is the CVSS score of CVE-2026-26186?
CVE-2026-26186 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-26186?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-26186, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-26186

Explore →

Is Your Infrastructure Affected by CVE-2026-26186?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.