dbcve.org
KibanaApplication · Elastic

CVE-2026-49094

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-28
Fix available
A fix is available. Upgrade to 8.19.16 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 viewer-level access can submit a request containing an oversized input value to an analytics collections management endpoint. Kibana will consume excessive CPU and memory resources while processing the request. This results in Kibana becoming unavailable to all users until the service is manually recovered.

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

An authenticated user with viewer-level access can submit oversized input values to Kibana's analytics collections management endpoint, causing excessive CPU and memory consumption during processing. This renders Kibana unavailable to all users until manually recovered.

MitigationImplement strict input size validation and request limits on analytics collections endpoints, and apply rate limiting for viewer-level users to prevent resource exhaustion 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

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 installed Kibana version
    Run `kibana --version` or check the version from the Kibana welcome page, or query the status endpoint at `GET /api/status`
    Affected if Version is 8.0.0 or higher but lower than 8.19.16
  2. Verify analytics collections feature is accessible
    Check if the Kibana analytics collections API endpoint `/api/analytics/collections` exists and responds to requests. This can be confirmed by reviewing Kibana plugin configuration or testing the endpoint with an authenticated user
    Affected if Analytics collections feature is enabled and accessible to users
  3. Confirm viewer role user access to analytics
    Review Kibana role mappings to determine if users with viewer-level privileges are assigned roles that grant access to the analytics collections management API. Check role definitions under Security or Stack Management > Roles
    Affected if Viewer-role users have permissions to access or manage analytics collections through the API
  4. Check for external request size limits
    Inspect any reverse proxy, load balancer, or API gateway configuration (e.g., nginx, HAProxy, AWS API Gateway) sitting in front of Kibana for request body size limits or input validation rules
    Affected if No request size limit or input validation is configured upstream from Kibana that would block oversized parameter values

Environment is affected if running Kibana version 8.0.0 through 8.19.15, the analytics collections feature is accessible, and viewer-role users can submit requests to the analytics collections management endpoint without external input validation or size limits in place.

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

Implement strict input size validation and request limits on analytics collections endpoints, and apply rate limiting for viewer-level users to prevent resource exhaustion attacks.

Recommended fix High confidence

8.19.16 or later

  1. 1. Back up your Kibana configuration and data directory before proceeding
  2. 2. Download Kibana version 8.19.16 or later from elastic.co/downloads/kibana
  3. 3. Stop the Kibana service (e.g., systemctl stop kibana or equivalent)
  4. 4. Install the new Kibana version using your package manager or manual extraction
  5. 5. Start the Kibana service (e.g., systemctl start kibana or equivalent)
  6. 6. Verify Kibana is operational and the analytics collections endpoint is functioning normally
  7. 7. Confirm the vulnerability is resolved by testing with a viewer-level account
Caveat Review Elastic Stack 8.19.x release notes for any breaking changes before upgrading

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-49094 — 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-49094 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