dbcve.org
KibanaApplication · Elastic

CVE-2026-49093

HIGH · 7.7 CVSS v3.1 Published 2026-05-28
Fix available
A fix is available. Upgrade to 9.3.3 or later.
See remediation →
83/100
Remediation priority · High
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
Server-Side Request Forgery (CWE-918) in Kibana can allow an authenticated user with connector management privileges to bypass the operator-configured connector allowlist, causing the Kibana server to issue outbound requests to destinations the egress controls were intended to block.

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

This is a Server-Side Request Forgery (SSRF) vulnerability (CWE-918) in Kibana where an authenticated user with connector management privileges can bypass the operator-configured connector allowlist. This allows the attacker to force the Kibana server to issue outbound requests to destinations that egress controls were designed to block, potentially exposing internal services or bypassing network segmentation.

MitigationRestrict connector management privileges to only essential personnel, review and tighten the connector allowlist to enforce strict egress controls, and monitor Kibana server outbound request logs for anomalies.

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:>= 9.3.0, < 9.3.3

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
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

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
    Check the Kibana version by examining the kibana package file or the Kibana server /api/status endpoint. For file-based inspection, locate the version file (typically in the Kibana installation directory, such as 'node_modules/@kbn/repo-info/local/kibana/package.json' or check the running service version via the status API).
    Affected if The installed version falls within the range >= 9.3.0 and < 9.3.3.
  2. Verify connector functionality is in use
    Examine the Kibana configuration file (kibana.yml) for any connector-related settings, or query the Kibana API endpoints under /api/actions to see if connectors have been created or configured.
    Affected if Connectors are configured or have been created in the Kibana instance.
  3. Review connector allowlist configuration
    Inspect the Kibana configuration (kibana.yml) for xpack.actions.allowlist or related connector security settings. Use the Kibana Management UI or API to list configured connectors and their allowed destinations.
    Affected if An allowlist is configured but may not be properly enforced due to the bypass vulnerability.
  4. Audit connector management privileges
    Review user and role definitions in Kibana (via Management > Security > Roles or the API) to identify which users have connector management privileges (actions or connectors privileges). Check the assignment of roles with actions:* or specific action privileges.
    Affected if Any authenticated user has connector management privileges beyond the minimal required set.

The environment is affected if Kibana version is >= 9.3.0 and < 9.3.3, connectors are in use, and users with connector management privileges exist, allowing potential SSRF bypass of configured allowlists.

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

Restrict connector management privileges to only essential personnel, review and tighten the connector allowlist to enforce strict egress controls, and monitor Kibana server outbound request logs for anomalies.

Recommended fix High confidence

Kibana 9.3.3 or later

  1. 1. Plan and schedule a maintenance window for the Kibana upgrade.
  2. 2. Back up your Kibana configuration, dashboards, and any custom settings.
  3. 3. Upgrade Kibana to version 9.3.3 or later. Use your package manager or download from https://www.elastic.co/downloads/kibana.
  4. 4. After upgrade, verify that the Kibana service starts successfully.
  5. 5. Test that connector functionality works correctly and that the allowlist bypass vulnerability is resolved.
Caveat Review the Elastic 9.3.3 release notes for any breaking changes or deprecations that may affect your deployment.

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

Fix this in Kibana Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,800
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,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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