Skip to main content
Menu
CVEs

CVE

Fleet denial of service via osquery result log submission

Fleet versions before 4.92.0 that accept osquery result logs from enrolled hosts are affected. Fixed in Fleet 4.92.0.

CVE-2026-130761EUVD-2026-129161Published Updated Summary written by a model

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 4.92.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 4.92.0.

Summary

Fleet has a denial of service flaw that lets a remote attacker with a valid enrolled host node key exhaust database connections and read replica capacity by sending one osquery result log request containing many distinct query names. The attack is carried out over the network without logging in as a user.

Original description

Fleet before 4.92.0 contains a denial of service vulnerability that allows enrolled hosts to trigger unbounded per-name database lookups by submitting osquery result logs. Attackers with a valid host node key can send one request to /api/osquery/log containing many distinct query names, exhausting database connections and read replica capacity.

Who should check

Teams running Fleet (github.com/fleetdm/fleet, Go) before 4.92.0 that have osquery hosts enrolled and submitting result logs to /api/osquery/log

“Unbounded per-name database lookups in osquery result log submission allow an enrolled host to cause denial of service”

github.com

cve.now Index

39Pcve.now Index 39 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach10/20Affects Go packages
  • Severity8.7/10CVSS 8.7
  • No patch0/5No signal

What would change the score

  • Would score about 84 if added to CISA KEV
  • Would score about 79 if CISA's SSVC rates exploitation active
  • Would score about 44 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 4.92.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130761 (Fleet before 4.92.0 Denial of Service via osquery Result Log Submission), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130761 (entry last updated 2026-11-18):
Affected:
- Go package github.com/fleetdm/fleet: fixed in 4.92.0
Fixed versions: 4.92.0.
Conditions (all must be true for the bug to be hit):
- Fleet versions before 4.92.0 that accept osquery result logs from enrolled hosts. (source: https://github.com/fleetdm/fleet/security/advisories/GHSA-7vhg-7cr9-2qjh)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130761 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130761 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/fleetdm/fleet/security/advisories/GHSA-7vhg-7cr9-2qjh
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130761
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130761"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Affected versions

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · fleetdm/fleet · Advisory GHSA-7vhg-7cr9-2qjh
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130761
RecordNVD · CVE-2026-130761

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130761

Is CVE-2026-130761 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

An enrolled host can degrade or deny service to the Fleet instance by exhausting database connections and read replica capacity.Source: github.com

Which versions are affected by CVE-2026-130761?

github.com/fleetdm/fleet (Go): before 4.92.0.Source: cve.now feed data

Am I affected, and how do I check?

Fleet versions before 4.92.0 that accept osquery result logs from enrolled hosts are in scope. To check, compare the Fleet server version you run against 4.92.0.Source: github.com

How do I fix CVE-2026-130761?

Upgrade Fleet to 4.92.0 or later, which resolves query names in a single batched lookup and caps the distinct names resolved per request.Source: github.com

More CVEs