dbcve.org
KibanaApplication · Elastic

CVE-2026-33464

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-28
Fix available
A fix is available. Upgrade to 8.19.16 / 9.3.5 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
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead to a denial of service via Excessive Allocation (CAPEC-130). An authenticated user holding a low-privileged role can submit a specially crafted, oversized payload to an internal Kibana API, causing the Kibana process to exhaust available resources and become unresponsive to all users until the service recovers or is restarted.

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

An authenticated user with low-privileged role can send a specially crafted oversized payload to an internal Kibana API endpoint, causing uncontrolled resource consumption that exhausts available memory/CPU and renders the entire Kibana instance unresponsive to all users until restart or recovery.

MitigationImplement input validation and size limits on internal Kibana APIs, enforce proper authorization checks to restrict low-privileged users from accessing sensitive internal endpoints, and consider rate limiting to prevent excessive resource allocation attacks.

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:>= 8.0.0, < 8.19.16>= 9.0.0, < 9.3.5= 9.4.0

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 installed Kibana version
    Run 'kibana --version' or check the Kibana home page, or query the /api/status endpoint
    Affected if The version falls within >= 8.0.0 and < 8.19.16, OR >= 9.0.0 and < 9.3.5, OR equals 9.4.0
  2. Verify low-privileged users exist
    Query Kibana security API (/_security/user) or check user management settings for any users assigned roles below 'editor' or 'admin' level
    Affected if There are users with low-privileged roles such as 'viewer', 'monitoring_user', or custom roles with limited permissions
  3. Confirm internal API accessibility
    Check Kibana configuration file (kibana.yml) for 'server.internalApi' settings and review network policies restricting access to internal endpoints
    Affected if Internal API endpoints are accessible to authenticated low-privileged users without additional restrictions
  4. Check for resource exhaustion indicators
    Monitor Kibana process memory usage (top/ps), node.js heap usage, and CPU utilization. Review Kibana logs for out-of-memory errors or slow request warnings
    Affected if Kibana process shows unusually high memory consumption, frequent GC pauses, or logs indicate resource exhaustion from API requests

Environment is affected if running a vulnerable Kibana version AND has low-privileged users with access to internal APIs, with observable or historical signs of resource exhaustion from oversized payloads.

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 8.19.16 / 9.3.5 or later
Fixed in 8.19.169.3.5
Interim mitigation

Implement input validation and size limits on internal Kibana APIs, enforce proper authorization checks to restrict low-privileged users from accessing sensitive internal endpoints, and consider rate limiting to prevent excessive resource allocation attacks.

Recommended fix High confidence

Upgrade to Kibana 8.19.16 (for 8.x line) or 9.3.5/9.4.1 (for 9.x line)

  1. 1. Backup your current Kibana configuration and any custom dashboards or visualizations.
  2. 2. Ensure your Elasticsearch cluster is running a compatible version that matches your target Kibana version.
  3. 3. Stop the Kibana service: `sudo systemctl stop kibana` (or equivalent for your setup).
  4. 4. Upgrade Kibana to version 8.19.16 (for 8.x installations) or 9.3.5/9.4.1 (for 9.x installations). Use your package manager or download from https://www.elastic.co/downloads/kibana.
  5. 5. Verify the integrity of the downloaded package using GPG signatures provided by Elastic.
  6. 6. Start the Kibana service: `sudo systemctl start kibana`.
  7. 7. Confirm Kibana starts successfully and is responsive: check service status and attempt to access the web interface.
  8. 8. Verify that existing dashboards, visualizations, and saved objects are intact.
Caveat Ensure Elasticsearch version is compatible with the target Kibana version; Elastic Stack components should run matching major versions

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

Fix this in Kibana Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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 locally
dbcve dependency scanner

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