CVE-2026-26186
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFleet 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceFleet device management software versions before 4.80.1 contain a SQL injection vulnerability in the ORDER BY clause handling. The `goqu.I()` function was used unsafely with the `order_key` query parameter, allowing authenticated attackers to escape identifier quoting and inject arbitrary SQL expressions. This enables blind SQL injection for data exfiltration via conditional expressions that alter result ordering, plus potential DoS through resource exhaustion.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 4.80.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Fleetdm Fleet versionCheck the installed Fleetdm Fleet version by reviewing the software build, container image tag, or the /api/version endpoint if exposed. Compare against the affected range of < 4.80.1.Affected if The installed version is below 4.80.1.
-
Confirm Fleetdm Fleet is runningVerify that the Fleetdm Fleet service is actively running and accessible. This could be a container, binary, or managed deployment.Affected if Fleetdm Fleet is running and accessible.
-
Locate the order_key query parameter handlerReview application or proxy logs for requests containing the 'order_key' parameter sent to Fleetdm endpoints. Check if the goqu.I() function is used in code handling sort/ordering operations.Affected if Requests with 'order_key' parameter are being processed by Fleetdm.
-
Check authentication configurationVerify whether authentication is enabled and enforced on Fleetdm API endpoints. Review role-based access control settings to determine which user roles can access endpoints accepting the order_key parameter.Affected if Authenticated users or certain roles can access the vulnerable endpoint.
You are affected if running any Fleetdm Fleet version below 4.80.1 where authenticated users can submit 'order_key' query parameters to the application.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.80.1
Upgrade to version 4.80.1 or later. If immediate patching is impossible, restrict access to the affected endpoint to trusted roles only and implement strict allow-listing of user-supplied sort/column parameters at the application or proxy layer.
Fleet version 4.80.1
- Upgrade Fleet to version 4.80.1 or later to resolve the SQL injection vulnerability
- Verify the upgrade was successful by confirming the version number in the Fleet admin interface or via command line
- If immediate upgrade is not feasible, implement network-level or application-layer restrictions to limit access to the affected endpoint to trusted roles only
- Configure an application or proxy layer to strictly allow-list user-supplied sort or column parameters (such as `order_key`), rejecting any unexpected input
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26186 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-26186 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data