dbcve.org
KibanaApplication · Elastic

CVE-2026-0543

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-13
Fix available
A fix is available. Upgrade to 8.19.0 / 9.1.10 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 Input Validation (CWE-20) in Kibana's Email Connector can allow an attacker to cause an Excessive Allocation (CAPEC-130) through a specially crafted email address parameter. This requires an attacker to have authenticated access with view-level privileges sufficient to execute connector actions. The application attempts to process specially crafted email format, resulting in complete service unavailability for all users until manual restart is performed.

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 Email Connector allows authenticated attackers with view-level privileges to send specially crafted email address parameters that trigger excessive memory allocation (CAPEC-130). This causes complete service unavailability for all users, requiring manual restart to recover.

MitigationImplement strict input validation on email connector parameters to reject malformed or specially crafted email addresses that could trigger excessive resource allocation. Consider adding resource limits and request size restrictions.

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:>= 7.0.0, <= 7.17.29>= 8.0.0, < 8.19.0>= 9.0.0, < 9.1.10>= 9.2.0, < 9.2.4

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. Determine installed Kibana version
    Run 'kibana --version' or check the version file in the Kibana installation directory (e.g., /usr/share/kibana/package.json or the version info in kibana.yml). Alternatively, query the Kibana API: GET /api/status and examine the 'version.number' field in the response.
    Affected if The version number falls within any of these ranges: 7.0.0-7.17.29, 8.0.0-8.18.x, 9.0.0-9.1.9, or 9.2.0-9.2.3.
  2. Verify Email Connector is enabled
    Check the Kibana configuration file (kibana.yml) for the presence of 'xpack.actions.enabled' set to true (default). Also check if any action connectors are defined by querying the API: GET /api/actions/connectors (requires authentication).
    Affected if Email Connector functionality is enabled in the Kibana configuration.
  3. Identify configured email connectors
    Query the actions API to list all connectors: GET /api/actions/connectors. Look for any connectors with 'actionTypeId' set to '.email' or 'email'.
    Affected if At least one email connector is configured and visible in the list.
  4. Check for recent email action executions
    Review Kibana logs (in the logs directory) for entries containing 'actions' and 'email' around the timestamp of any service availability issues. Look for patterns indicating email action execution.
    Affected if Email connector actions have been executed, indicating active usage of the vulnerable component.

You are affected if your Kibana version is within the affected ranges AND the Email Connector feature is enabled or any email connectors are configured in your environment.

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.

From vendor data
Upgrade available Upgrade to 8.19.0 / 9.1.10 / 9.2.4 or later
Fixed in 8.19.09.1.109.2.4
Interim mitigation

Implement strict input validation on email connector parameters to reject malformed or specially crafted email addresses that could trigger excessive resource allocation. Consider adding resource limits and request size restrictions.

Fix this in Kibana Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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