dbcve.org
KibanaApplication · Elastic

CVE-2026-26940

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-19
Fix available
A fix is available. Upgrade to 8.19.13 / 9.2.7 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
Improper Validation of Specified Quantity in Input (CWE-1284) in the Timelion visualization plugin in Kibana can lead Denial of Service via Excessive Allocation (CAPEC-130). The vulnerability allows an authenticated user to send a specially crafted Timelion expression that overwrites internal series data properties with an excessively large quantity value.

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

The Timelion visualization plugin in Kibana fails to properly validate quantity values in user-supplied expressions, allowing authenticated users to overwrite internal series data properties with excessively large values. This causes excessive memory allocation leading to denial of service.

MitigationImplement strict input validation for quantity values in Timelion expressions to reject or cap excessively large values, and consider adding resource limits for query 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:>= 8.0.0, < 8.19.13>= 9.0.0, < 9.2.7>= 9.3.0, < 9.3.2

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 installation and version
    Run 'kibana --version' or check the version file in the Kibana installation directory (e.g., /usr/share/kibana/package.json or the version file in the Kibana root directory)
    Affected if The installed version falls within >= 8.0.0 and < 8.19.13, OR >= 9.0.0 and < 9.2.7, OR >= 9.0.0 and < 9.2.7, OR >= 9.3.0 and < 9.3.2
  2. Confirm Timelion plugin is enabled
    In Kibana, navigate to Stack Management > Kibana > Plugins, or check kibana.yml for 'timelion.enabled: false'. By default Timelion is enabled. Verify the plugin status via the Kibana API at '/api/status' or by checking if Timelion visualizations are accessible in the Visualize tab
    Affected if Timelion plugin is enabled and accessible to authenticated users
  3. Check for existing Timelion visualizations
    Search the Kibana .kibana index (via Dev Tools or Elasticsearch) for documents of type 'timelion-sheet' or 'visualization' with 'visState' containing 'title' references to Timelion, using: GET /.kibana/_search { "query": { "term": { "type": { "value": "timelion-sheet" } } } }
    Affected if Timelion visualizations exist and are available to authenticated users in the environment

You are affected if Kibana version is within the affected ranges AND the Timelion plugin is enabled and accessible to authenticated users who can create or modify Timelion expressions.

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.13 / 9.2.7 / 9.3.2 or later
Fixed in 8.19.139.2.79.3.2
Interim mitigation

Implement strict input validation for quantity values in Timelion expressions to reject or cap excessively large values, and consider adding resource limits for query operations.

Recommended fix High confidence

Kibana 8.19.13 for 8.x versions; Kibana 9.2.7 for 9.0-9.2.x versions; Kibana 9.3.2 for 9.3.0-9.3.1 versions

  1. 1. Identify your current Kibana version using Kibana'sAbout page or the/_status API
  2. 2. Determine the appropriate upgrade path based on your current major version (8.x or 9.x)
  3. 3. Review Elastic's upgrade documentation for your specific version jump at https://www.elastic.co/guide/en/kibana/current/upgrade.html
  4. 4. Create a backup of your Kibana configuration and saved objects
  5. 5. Test the upgrade in a staging environment before production deployment
  6. 6. Upgrade Kibana to the fixed version: 8.19.13 (for 8.x users) or 9.2.7/9.3.2 (for 9.x users)
  7. 7. Verify the Timelion plugin functions correctly after upgrade
  8. 8. Monitor Kibana logs for any errors or anomalies
Caveat Review Elastic Stack Upgrade Guide for potential breaking changes between your current version and target version, particularly around deprecated features and configuration changes

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