KibanaApplication · Elastic
CVE-2026-26937
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 · uneditedUncontrolled Resource Consumption (CWE-400) in the Timelion component in Kibana can lead Denial of Service via Input Data Manipulation (CAPEC-153)
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 confidenceUncontrolled resource consumption vulnerability in Kibana's Timelion component allows attackers to cause denial of service through malicious input data manipulation. The lack of proper input validation or resource limits on Timelion queries enables excessive consumption of memory, CPU, or other system resources.
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
>= 8.0.0, < 8.19.11>= 9.0.0, < 9.2.5CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Kibana versionRun 'kibana --version' or check the version file in the Kibana installation directory, or query the Kibana API endpoint /api/statusAffected if The installed version is >= 8.0.0 and < 8.19.11, or >= 9.0.0 and < 9.2.5
-
Verify Timelion is enabledCheck the Kibana configuration file (kibana.yml) for enabled plugins, or query the /api/status endpoint to list installed pluginsAffected if Timelion plugin is present and enabled in the Kibana instance
-
Check Timelion plugin accessibilityAttempt to access the Timelion UI at /app/timelion or verify the timelion endpoint responds to requestsAffected if Timelion is exposed and accessible to users who can submit queries
-
Inspect for resource limit configurationsReview kibana.yml for settings related to timelion.query.timeout, timelion.max_bucket, or similar resource limit parametersAffected if No query timeout, complexity limits, or input size restrictions are configured for Timelion
The environment is affected if Kibana version is within the vulnerable range AND Timelion is enabled and accessible without configured resource limits on queries.
Generated from the published advisory. Verify against your own configuration.
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 · scoped8.19.119.2.5
Implement input validation and resource limits on Timelion queries to constrain resource consumption. Consider adding query complexity limits, execution timeouts, and input size restrictions.
Kibana 8.19.11+ (8.x branch) or Kibana 9.2.5+ (9.x branch)
- Upgrade Kibana to version 8.19.11 or later for the 8.x branch
- Upgrade Kibana to version 9.2.5 or later for the 9.x branch
- After upgrading, verify that the Timelion functionality works correctly and that the resource consumption issue is resolved
- Monitor Kibana logs for any errors or resource usage anomalies following the upgrade
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
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26937 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-26937 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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