dbcve.org
KibanaApplication · Elastic

CVE-2026-26935

HIGH · 7.5 CVSS v3.1 Published 2026-02-26
Fix available
A fix is available. Upgrade to 8.19.12 / 9.2.6 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 Input Validation (CWE-20) in the internal Content Connectors search endpoint 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 confidence

Improper input validation in Kibana's internal Content Connectors search endpoint allows attackers to manipulate input data, causing excessive resource consumption and denial of service. The vulnerability stems from the endpoint's failure to properly sanitize or validate search query parameters before processing.

MitigationApply Kibana security patches addressing the Content Connectors search endpoint input validation. If no patch available, implement input validation and request rate limiting on the affected endpoint as a compensating control.

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.4.0, < 8.19.12>= 9.0.0, < 9.2.6= 9.3.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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Kibana version
    Run 'kibana --version' or check the version from the Kibana welcome page, or query the Kibana API at /api/status
    Affected if The installed version is >= 8.4.0 and < 8.19.12, OR >= 9.0.0 and < 9.2.6, OR exactly 9.3.0
  2. Confirm Content Connectors feature is enabled
    Review kibana.yml for content_connectors.enabled setting or query the Kibana plugins API to list active plugins related to content connectors
    Affected if Content Connectors plugin or feature is enabled in the Kibana configuration
  3. Check if the vulnerable endpoint is accessible
    Review network exposure of Kibana and verify whether internal API endpoints (specifically /api/content/connectors/search or similar search endpoints) are accessible to untrusted users or external networks
    Affected if The Content Connectors search endpoint is exposed to untrusted users or the network without proper access controls
  4. Verify Kibana is exposed to network
    Check firewall rules, reverse proxy configuration, and Kibana's server.host setting to determine if Kibana listens on non-localhost interfaces
    Affected if Kibana is reachable from network segments containing untrusted users or systems

A user is affected if they run a vulnerable Kibana version (in the affected ranges) with Content Connectors enabled and the endpoint is accessible to attackers.

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.12 / 9.2.6 or later
Fixed in 8.19.129.2.6
Interim mitigation

Apply Kibana security patches addressing the Content Connectors search endpoint input validation. If no patch available, implement input validation and request rate limiting on the affected endpoint as a compensating control.

Recommended fix High confidence

Kibana 8.19.12+ (8.x) or 9.2.6+/9.3.1+ (9.x)

  1. 1. Identify the current Kibana version by checking the Kibana logs or status endpoint
  2. 2. For Kibana 8.x deployments: plan upgrade to version 8.19.12 or later
  3. 3. For Kibana 9.x deployments: plan upgrade to version 9.2.6 or later, or version 9.3.1 or later
  4. 4. Review Elastic Kibana upgrade documentation for your deployment type (including any intermediate upgrades if jumping multiple minor versions)
  5. 5. Perform the upgrade following standard Elastic upgrade procedures
  6. 6. Verify Kibana starts successfully and the Content Connectors functionality works
  7. 7. Monitor for any anomalies in Kibana service stability
Caveat Review Elastic Stack upgrade guide for potential breaking changes between your current version and target version; major version upgrades (8.x to 9.x) may require additional migration steps

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

Fix this in Kibana Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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