dbcve.org
KibanaApplication · Elastic

CVE-2026-0530

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 request. This causes the application to perform redundant processing operations that continuously consume system resources until service degradation or complete unavailability occurs.

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

This is a resource exhaustion vulnerability in Kibana Fleet where specially crafted requests cause the application to perform redundant processing operations that continuously consume system resources, leading to service degradation or complete unavailability. The vulnerability stems from lack of proper resource limits or throttling (CWE-770) on certain Fleet endpoints.

MitigationImplement rate limiting, request throttling, or resource quotas on the affected Kibana Fleet endpoints to prevent excessive resource allocation. Apply vendor patches when available.

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. Verify Kibana Fleet is enabled
    Check the Kibana configuration file (kibana.yml) for 'xpack.fleet.enabled' setting set to true, or check via Kibana Stack Management > Fleet > Settings to confirm Fleet plugin is active
    Affected if Fleet is enabled and running
  2. Determine installed Kibana version
    Run 'kibana --version' or check the Kibana about page (Kibana > Stack Management > About) to obtain the exact version number
    Affected if Version falls within affected ranges: 7.10.0 to 7.17.28, 8.0.0 to 8.19.9, 9.0.0 to 9.1.9, or 9.2.0 to 9.2.3
  3. Confirm Fleet API endpoints are accessible
    Verify Kibana can process Fleet-related API requests by checking that Fleet-specific APIs respond (for example, /api/fleet/agents or /api/fleet/package policies endpoints)
    Affected if Fleet endpoints are reachable without existing rate limiting restrictions
  4. Check for existing resource throttling configuration
    Inspect Kibana configuration (kibana.yml) or any reverse proxy/load balancer in front of Kibana for rate limit, throttling, or request timeout settings related to Fleet routes
    Affected if No rate limiting, throttling, or resource quotas are configured on Fleet endpoints

User is affected if Kibana Fleet is enabled AND the installed Kibana version falls within the affected version ranges AND no resource limits are configured on Fleet endpoints.

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 rate limiting, request throttling, or resource quotas on the affected Kibana Fleet endpoints to prevent excessive resource allocation. Apply vendor patches when available.

Recommended fix High confidence

7.17.29 (for 7.x), 8.19.10 (for 8.x), 9.1.10 (for 9.0.x), 9.2.4 (for 9.2.x)

  1. 1. Identify the current Kibana version by checking the Kibana About page or the kibana.yml configuration file
  2. 2. For Kibana 7.x (7.10.0 to 7.17.28): Upgrade to version 7.17.29 or later
  3. 3. For Kibana 8.x (8.0.0 to 8.19.9): Upgrade to version 8.19.10 or later
  4. 4. For Kibana 9.0.x (9.0.0 to 9.1.9): Upgrade to version 9.1.10 or later
  5. 5. For Kibana 9.2.x (9.2.0 to 9.2.3): Upgrade to version 9.2.4 or later
  6. 6. After upgrade, verify Fleet functionality works correctly and monitor resource usage
Caveat Elastic stack version compatibility must be maintained; ensure Elasticsearch version matches Kibana major version

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

Fix this in Kibana Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0530 — 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-0530 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