NVD / CVE Program· CNA GitHub_M

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

MediumCVSS 5.1 · v4.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 20/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.35% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: github.com/fleetdm/fleet/v4 (Go) 4.80.1; govulncheck-vulndb (openSUSE:Leap 15.6) 0.0.20260317T205859-150000.1.152.1.

Low priority for now. Upgrade to github.com/fleetdm/fleet/v4 (Go) 4.80.1; govulncheck-vulndb (openSUSE:Leap 15.6) 0.0.20260317T205859-150000.1.152.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

SQL injection

Published: Feb 25, 2026
Updated: Jun 17, 2026
EPSS: 0.3% · 28th percentile
CWE: CWE-89

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 20 / 40 · 5.1 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitHub_M: 5.1; NVD has not scored this yet; the score shown is the CNA’s.

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
fleetdm	fleet	cpe:2.3:a:fleetdm:fleet

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

fleetdm fleet
- < 4.80.1affected

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

fleetdm fleetbefore 4.80.1

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Go	github.com/fleetdm/fleet/v4	before 4.80.1	4.80.1
openSUSE:Leap 15.6	govulncheck-vulndb	before 0.0.20260317T205859-150000.1.152.1	0.0.20260317T205859-150000.1.152.1

Same product

fleetdm: all records

Other highest-scoring records for the same primary product.

CVE-2020-26276SAML authentication vulnerability in Fleet
40Plan
CVE-2026-103264Fleet before 4.87.0 Authentication Bypass via Device Identifiers
37Monitor
CVE-2026-23518Fleet has a JWT signature bypass vulnerability in Azure AD MDM enrollment
37Monitor

Published before and after this one in the same product

← EarlierCVE-2026-22808Jan 21, 2026 · Fleet Windows MDM endpoint has a Cross-site Scripting vulnerability
22Monitor
← EarlierCVE-2026-23517Jan 21, 2026 · Fleet has an Access Control vulnerability in debug/pprof endpoints
25Monitor
Later →CVE-2026-23999Feb 25, 2026 · Fleet: Device lock PIN can be predicted if lock time is known
2Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Go:github.com/fleetdm/fleet/v4	4.80.1	Package registry (OSV)
opensuse:govulncheck-vulndb	0.0.20260317T205859-150000.1.152.1 · openSUSE:Leap 15.6	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-54245182 days apartFleet: SQL injection in Okta conditional access endpoint allows host-controlled compromise of the Fleet database
30Monitor
CVE-2026-46370182 days apartFleet has observer-level enrollment secret extraction via ORDER BY oracle on labels host-listing endpoint
26Monitor
CVE-2026-46371182 days apartFleet: Observer-level enrollment secret extraction via ORDER BY oracle on Apple MDM commands endpoint
26Monitor
CVE-2026-3438630 days apartFleet vulnerable to SQL injection in MDM bootstrap package by authenticated team or global admin
25Monitor
CVE-2026-3438530 days apartFleet's Apple MDM profile delivery has second-order SQL injection that can compromise the database
24Monitor
CVE-2026-101046214 days apartFleet before 4.89.0 SQL Injection via ORDER BY Activity Endpoints
9Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

CVE-2026-240040 days apartFleet: Unauthenticated Android device disenrollment vulnerability via Pub/Sub endpoint
6Monitor

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: X

Weakness class (CWE)

CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

CVSS 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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

The query text is built by concatenating user input. The database cannot tell where the data ends and the command begins.

The bug in code

The whole CWE-89 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const owner = req.query.owner;
2const rows = await db.query(
3  "SELECT * FROM files WHERE owner = '" + owner + "'"
4);

Fixed

1const owner = req.query.owner;
2const rows = await db.query(
3  "SELECT * FROM files WHERE owner = $1",
4  [owner]
5);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log (1)

Fix✗ → ✓Sep 28, 2026, 10:46 PM UTC

For records you follow, these changes also arrive as notifications. →

References

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

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records