dbcve.org
KibanaApplication · Elastic

CVE-2026-33459

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-08
Fix available
A fix is available. Upgrade to 8.19.14 / 9.2.8 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 denial of service via Excessive Allocation (CAPEC-130). An authenticated user with access to the automatic import feature can submit specially crafted requests with excessively large input values. When multiple such requests are sent concurrently, the backend services become unstable, resulting in service disruption and deployment unavailability for 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 · high confidence

Uncontrolled resource consumption vulnerability in Kibana's automatic import feature allows authenticated users to submit specially crafted requests with excessively large input values. When multiple concurrent requests are sent, backend services become unstable due to resource exhaustion, causing denial of service for all users.

MitigationImplement input validation and size limits on the automatic import feature to restrict excessively large values; consider adding rate limiting or throttling for concurrent requests to prevent resource exhaustion.

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.15.0, < 8.19.14>= 9.0.0, < 9.2.8>= 9.3.0, < 9.3.3

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. Check Kibana version
    Run `kibana --version` or check the version field in the Kibana status API response (GET /api/status). Compare the installed version against the affected ranges: >= 8.15.0 and < 8.19.14, >= 9.0.0 and < 9.2.8, or >= 9.3.0 and < 9.3.3.
    Affected if The installed version falls within any of the listed affected ranges.
  2. Identify if automatic import feature is in use
    Review Kibana configuration for saved objects imports, data imports, or dashboard imports initiated automatically. Check access logs for requests to import-related API endpoints (such as /api/saved_objects/_import, /api/import) with abnormally large parameter sizes.
    Affected if The automatic import feature is enabled and actively processing user requests with large parameter values.
  3. Monitor for resource exhaustion signs
    Observe Kibana backend service CPU and memory consumption. Check for spikes in resource usage correlating with import operations, or look for increased error rates indicating service instability.
    Affected if Backend services show excessive resource consumption during import feature usage, leading to degraded availability.

You are affected if running a Kibana version in the affected ranges AND the automatic import feature is in use, enabling authenticated users to submit requests with excessively large values that cause service instability.

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.14 / 9.2.8 / 9.3.3 or later
Fixed in 8.19.149.2.89.3.3
Interim mitigation

Implement input validation and size limits on the automatic import feature to restrict excessively large values; consider adding rate limiting or throttling for concurrent requests to prevent resource exhaustion.

Recommended fix High confidence

Kibana 8.19.14 (for 8.x users), 9.2.8 (for 9.0-9.2.x users), or 9.3.3 (for 9.3.x users)

  1. Identify your current Kibana version using 'kibana --version' or the Kibana management UI
  2. Determine which version branch you are on (8.x or 9.x)
  3. For Kibana 8.15.0 to 8.19.13: upgrade to version 8.19.14
  4. For Kibana 9.0.0 to 9.2.7: upgrade to version 9.2.8
  5. For Kibana 9.3.0 to 9.3.2: upgrade to version 9.3.3
  6. After upgrading, verify the automatic import feature functions correctly
  7. Monitor for any service disruptions during and after the upgrade
Caveat Review Elastic Stack upgrade notes for potential breaking changes between minor versions; test in staging environment before production deployment

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

Fix this in Kibana Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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