EUVD-2026-33035
GHSA-qf29-h8cg-2hg4
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with connector management rights
-
DeliveryCreate or edit connector with blocked internal destination
-
ExploitBypass operator egress allowlist
-
ExecutionTrigger connector to issue server-side request
-
ImpactExfiltrate response from restricted service
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Credential Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated Kibana account that has been granted connector (Actions) management privileges, and requires that the operator has configured a connector allowlist / egress restriction that the attacker then bypasses. The vulnerability is only meaningful where such egress controls exist and where connector management is delegated to users who are not fully trusted; a single-operator deployment with no delegated connector rights has little exposure. Limiting factors: authenticated (PR:L) access is mandatory, no unauthenticated path exists, and impact is confined to confidentiality of reachable destinations (I:N/A:N). Affected deployments are limited to Kibana 9.3.0-9.3.2. |
| Impact | The signals here are consistent and point to a real-but-not-urgent issue. CVSS 3.1 is 7.7 (High) with AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N - network-reachable, low complexity, but requiring an authenticated account with connector management privileges, with a scope change and high confidentiality impact and no integrity or availability impact. EPSS is 0.03% (9th percentile), and CISA SSVC scores Exploitation: none, Automatable: no, Technical Impact: partial, all of which argue against mass or automated exploitation. This is NOT in CISA KEV and no POC has been identified. The privilege requirement (PR:L, connector management) is the dominant limiting factor: this is primarily a post-authentication, insider or compromised-privileged-account risk rather than an internet-wide worm-able threat. Priority should be normal patch-cycle for internet-exposed or multi-tenant Kibana deployments where connector management is delegated to less-trusted users; low priority for single-operator internal deployments. No conflicting data was identified - CVSS vector, EPSS, and SSVC all align. |
| Exploit ScenarioDerived | An analyst or automation user who has been granted connector management rights in a shared Kibana instance crafts or edits a connector whose destination points at an internal-only service (for example a cloud metadata endpoint or an internal admin API) that the operator allowlist was configured to block. Triggering the connector causes the Kibana server to issue the outbound request from its trusted network position and return the response data to the attacker. No public exploit code has been identified, and the low attack complexity (AC:L) means the main barrier is obtaining the connector management privilege. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Jul 21, 2026
Server-Side Request Forgery in Elastic Kibana 9.3.0 through 9.3.2 lets an authenticated user holding connector management privileges override the operator-configured connector allowlist and force the Kibana server to make outbound requests to destinations that egress controls were meant to block. Because the request originates from the trusted server, an attacker can reach internal or otherwise restricted network services and exfiltrate their responses. EPSS is very low (0.03%, 9th percentile) and there is no public exploit identified at time of analysis, but the scope-changing CVSS 7.7 rating reflects meaningful confidentiality impact against internal assets.
Earlier versions of this analysis (1)
Server-Side Request Forgery in Kibana allows an authenticated user holding connector management privileges to bypass the operator-configured connector allowlist, forcing the Kibana server to issue outbound HTTP requests to destinations that egress controls were explicitly designed to block. The CVSS Changed Scope (S:C) combined with high confidentiality impact (C:H) means successful exploitation extends beyond Kibana itself, potentially exposing sensitive internal network resources such as cloud metadata services or internal APIs reachable from the Kibana host. No public exploit code has been identified and this vulnerability is not listed in the CISA KEV catalog at time of analysis.
RemediationAI
Vendor-released patch: upgrade to Kibana 9.3.3, which contains the fix per Elastic advisory ESA-2026-40 (https://discuss.elastic.co/t/kibana-9-3-3-security-update-esa-2026-40/386562). Until you can upgrade, restrict who holds connector management privileges to a minimal set of fully trusted operators, since exploitation requires that role - review and revoke delegated connector-management access for lower-trust or multi-tenant users, accepting the trade-off that those users can no longer create or edit connectors. As a network-layer compensating control, enforce the egress restriction outside Kibana by placing the Kibana server behind an outbound proxy or firewall that limits permitted destinations, so an in-app allowlist bypass still cannot reach internal services; the side effect is that legitimate connectors to new destinations must be whitelisted at the proxy. Do not rely on the in-application connector allowlist alone on affected versions.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Kibana is the visualization and management front-end of the Elastic Stack; its Actions/Connectors framework lets it issue outbound HTTP requests to external systems (webhooks, incident-management tools, LLM/email endpoints, etc.) as part of alerting and automation. Operators can restrict where connectors are allowed to send traffic via an egress/URL allowlist so the server cannot be abused as a pivot. This flaw is a classic CWE-918 Server-Side Request Forgery: the allowlist validation can be bypassed by a user with connector management rights, so the server-side request logic honors an attacker-influenced destination instead of the policy-approved one. The vulnerable code path is the connector configuration/execution layer where the destination URL is validated against the operator allowlist before Kibana dispatches the request. Affected component per CPE: cpe:2.3:a:elastic:kibana.
Know when Kibana gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Network-reachable SSRF requiring an authenticated connector-management account (PR:L), no user interaction, scope change to internal targets (S:C) with confidentiality-only impact (C:H, I:N/A:N).
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
3DescriptionNVD
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.
Executive ViewAI
Elastic Kibana 9.3.0-9.3.2 contains a server-side request forgery vulnerability that allows authenticated users with connector management permissions to bypass egress controls and force the Kibana server to access internal networks and restricted services. This directly undermines network segmentation and data protection controls, exposing internal infrastructure to unauthorized reconnaissance and potential exfiltration. Organizations running affected versions must immediately audit connector permissions and implement network-layer mitigations pending availability of a vendor patch.
Restrict connector management permissions to a minimal privileged administrative group; implement firewall egress rules limiting Kibana server outbound access to pre-approved internal and external destinations only; enable detailed audit logging of connector lifecycle events; consider network segmentation to isolate Kibana servers from sensitive internal services until a patched version is deployed.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
VulDB
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.
Kibana versions before 5.6.15 and 6.6.1 contain an arbitrary code execution flaw in the Timelion visualizer. Rated criti
Kibana versions 6.7.0 to 6.8.8 and 7.0.0 to 7.6.2 contain a prototype pollution flaw in the Upgrade Assistant. Rated hig
Kibana versions before 6.4.3 and 5.6.13 contain an arbitrary file inclusion flaw in the Console plugin. Rated critical s
Prototype pollution in Kibana leads to arbitrary code execution via a crafted file upload and specifically crafted HTTP
Kibana versions 4.0 to 4.6, 5.0 to 5.6.12, and 6.0 to 6.4.2 contain an error in the way authorization credentials are us
A Prototype pollution vulnerability in Kibana leads to arbitrary code execution via crafted HTTP requests to machine lea
Kibana versions before 6.6.1 contain an arbitrary code execution flaw in the security audit logger. Rated critical sever
Prototype Pollution in Kibana can lead to code injection via unrestricted file upload combined with path traversal. Rate
Authorization bypass in Kibana's Fleet package installation process lets an authenticated user who holds delegated Fleet
Privilege escalation in Elastic Kibana's Agent Builder component (versions 9.4.0-9.4.3) allows authenticated low-privile
A deserialization issue in Kibana can lead to arbitrary code execution when Kibana attempts to parse a YAML document con
Kibana version 8.7.0 contains an arbitrary code execution flaw. Rated high severity (CVSS 8.8), this vulnerability is re
Exploit-DB