dbcve.org
KibanaApplication · Elastic

CVE-2026-0531

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-13
Fix available
A fix is available. Upgrade to 7.17.29 / 8.19.10 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Allocation of Resources Without Limits or Throttling (CWE-770) in Kibana Fleet can lead to Excessive Allocation (CAPEC-130) via a specially crafted bulk retrieval request. This requires an attacker to have low-level privileges equivalent to the viewer role, which grants read access to agent policies. The crafted request can cause the application to perform redundant database retrieval operations that immediately consume memory until the server crashes and becomes unavailable to all users.

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 · moderate confidence

Kibana Fleet's bulk retrieval endpoint lacks proper resource limits or throttling (CWE-770). An attacker with viewer-level privileges can send specially crafted bulk requests that trigger redundant database retrieval operations, causing excessive memory allocation until the server crashes and becomes unavailable.

MitigationImplement request size limits, rate limiting, and resource throttling on Fleet bulk retrieval endpoints. Add proper resource cleanup and pooling to prevent redundant database operations.

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
KibanaApplication
Affected:>= 7.10.0, < 7.17.29>= 8.0.0, < 8.19.10>= 9.0.0, < 9.1.10>= 9.2.0, < 9.2.4

CVSS 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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Kibana version
    Run 'kibana --version' or check the version field in /usr/share/kibana/package.json, or query the Kibana API at GET /api/status
    Affected if The version is 7.10.0 through 7.17.28, 8.0.0 through 8.19.9, 9.0.0 through 9.1.9, or 9.2.0 through 9.2.3
  2. Confirm Fleet plugin is enabled
    Check the kibana.yml configuration file for Fleet settings under 'xpack.fleet' or look for the Fleet plugin in the Kibana plugins directory
    Affected if Fleet plugin is installed and enabled in the Kibana configuration
  3. Verify viewer-level user roles exist
    Check Kibana security role definitions for users assigned the 'viewer' role or equivalent read-only Fleet permissions
    Affected if Users with viewer-level or read-only Fleet privileges are present in the system
  4. Check Fleet bulk API endpoint exposure
    Review Kibana's API routes for exposed Fleet bulk retrieval endpoints, typically under /api/fleet/.../bulk paths
    Affected if The Fleet bulk retrieval endpoint is accessible without additional rate limiting configured at the proxy or application layer

You are affected if your Kibana version falls within the affected ranges AND the Fleet plugin is enabled AND users with viewer-level privileges can access the Fleet bulk retrieval endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.17.29 / 8.19.10 / 9.1.10 or later
Fixed in 7.17.298.19.109.1.10
Interim mitigation

Implement request size limits, rate limiting, and resource throttling on Fleet bulk retrieval endpoints. Add proper resource cleanup and pooling to prevent redundant database operations.

Recommended fix High confidence

Upgrade to the first fixed version in your major release line: 7.17.29 (7.x), 8.19.10 (8.x), 9.1.10 (9.0.x), or 9.2.4 (9.2.x)

  1. 1. Backup your current Kibana configuration and data directory
  2. 2. Review the Kibana upgrade guide for your current major version: https://www.elastic.co/guide/en/kibana/current/upgrade.html
  3. 3. Plan maintenance window as Kibana will require restart
  4. 4. For Kibana 7.x: Upgrade to version 7.17.29 or later
  5. 5. For Kibana 8.x: Upgrade to version 8.19.10 or later
  6. 6. For Kibana 9.0.x: Upgrade to version 9.1.10 or later
  7. 7. For Kibana 9.2.x: Upgrade to version 9.2.4 or later
  8. 8. After upgrade, restart Kibana service to apply changes
Caveat Standard Kibana upgrade risks apply - review breaking changes in Elastic Stack release notes for your target version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Kibana Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0531 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0531 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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