Security readout for executives and security teams
Plain-English summary
Fleet versions before 4.80.1 have an authenticated SQL injection flaw in a sorting parameter. A logged-in user could potentially infer sensitive database information or degrade service performance. The vendor states 4.80.1 fixes the issue. There is no provided evidence of active exploitation.
Executive priority
Treat as a timely remediation item for Fleet environments, especially multi-user or delegated-admin deployments. It is not currently described as actively exploited, but it can expose sensitive database information and affect availability. Upgrade during the next appropriate maintenance window or sooner for higher-trust-risk environments.
Technical view
CVE-2026-26186 is CWE-89 in Fleet’s `order_key` query parameter. Unsafe use of `goqu.I()` in an `ORDER BY` clause allowed crafted input to escape identifier quoting and become executable SQL expressions. Sources describe blind SQL injection impact, possible query failures, and excessive computation, but no demonstrated stacked queries or reliable data modification.
Likely exposure
Organizations running Fleet versions earlier than 4.80.1 are exposed if authenticated users can access the affected endpoint. Exposure is higher where broad user roles or untrusted authenticated users can supply sorting parameters.
Exploitation context
The attacker needs authenticated access. The issue is network-reachable and low-complexity, but limited to an `ORDER BY` context. Sources support data disclosure through blind inference and potential availability impact. KEV status is false, and no cited source reports active exploitation.
Researcher notes
The public description attributes the flaw to backtick escape behavior around identifier handling in `ORDER BY`. Evidence supports blind SQL injection and possible denial-of-service effects. The source bundle does not provide exploit proof, endpoint details, or evidence of direct data modification.
Mitigation direction
- Upgrade Fleet to version 4.80.1 or later.
- Restrict affected endpoint access to trusted roles if immediate upgrade is not possible.
- Allow-list user-supplied sort or column parameters at the application or proxy layer.
- Review vendor advisory for any updated remediation guidance.
Validation and detection
- Inventory Fleet deployments and identify versions earlier than 4.80.1.
- Confirm whether authenticated users can access the affected endpoint.
- Review application or proxy controls for strict allow-listing of sort parameters.
- Check Fleet release status to verify upgrade to 4.80.1 or later.
- Monitor database and application errors for abnormal sorting-related query failures.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-26186 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.1 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N/E:U
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N/E:U——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
5.1MediumVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N/E:U
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/fleetdm/fleet/security/advisories/GHSA-49xw-vfc4-7p43CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
