What is the CVSS score of CVE-2026-49095?

CVE-2026-49095 has a CVSS 3.1 base score of 6.5 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N. EPSS exploitation probability: 0.0%.

Which versions of Kibana Fleet are affected by CVE-2026-49095?

Elastic Kibana's Fleet agent policy management feature contains a privilege escalation vulnerability (CVE-2026-49095, CVSS 7.2) allowing authenticated Fleet administrators to inject elevated…

How to fix or mitigate CVE-2026-49095?

Within 24 hours: Restrict Fleet administrator role to only essential personnel and audit recent Fleet policy modifications for suspicious API key injections. Within 7 days: Verify all Fleet-provisioned API keys have appropriate scope limitations aligned with least-privilege principles and enable Elasticsearch audit logging for security index access. Within 30 days: Monitor Elastic security advisories for a patch release and establish policy review procedures for Fleet agent configurations.

Kibana Fleet CVE-2026-49095

EUVD-2026-33033 MEDIUM

Improper Input Validation (CWE-20)

2026-05-28 elastic

GHSA-p9vc-h7rw-q6hq

Privilege Escalation Elastic Kibana

6.5

CVSS 3.1 · Vendor: elastic

Severity by source

Vendor (elastic) PRIMARY

6.5 MEDIUM

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

Primary rating from Vendor (elastic) · only source for this CVE.

CVSS VectorVendor: elastic

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Lifecycle Timeline

Severity Changed

May 28, 2026 - 21:22 NVD

HIGH MEDIUM

CVSS changed

May 28, 2026 - 21:22 NVD

7.2 (HIGH) 6.5 (MEDIUM)

Analysis Generated

May 28, 2026 - 21:21 vuln.today

DescriptionCVE.org

Improper Input Validation (CWE-20) in the Kibana Fleet agent policy management feature can lead to privilege escalation. An authenticated user with Fleet management privileges can manipulate agent policy configuration by injecting values into a configuration override mechanism that is not adequately validated. An attacker can cause Elastic Agents to be issued API keys with elevated Elasticsearch privileges, potentially granting unauthorized read and write access to sensitive Elasticsearch security indices beyond what is intended for the Fleet management role.

AnalysisAI

Privilege escalation in Elastic Kibana's Fleet agent policy management feature allows authenticated Fleet administrators to inject unvalidated values into a configuration override mechanism, causing Elastic Agents to be provisioned with API keys carrying elevated Elasticsearch privileges. Successful exploitation yields unauthorized read/write access to sensitive Elasticsearch security indices beyond the Fleet role's intended scope. No public exploit identified at time of analysis, and CISA KEV does not list this issue.

Technical ContextAI

Kibana Fleet is the centralized management plane for Elastic Agents, used to push integration policies and credentials to fleet-managed endpoints. When an administrator defines or updates an agent policy, Kibana mints Elasticsearch API keys that the agents use to ship data to specified indices. The vulnerability is rooted in CWE-20 (Improper Input Validation): a configuration override path within agent policy management accepts attacker-controlled fields without enforcing that the resulting API key privileges remain within the Fleet role's authorization boundary, effectively allowing role-scope confusion at the Elasticsearch RBAC layer. The affected component is identified by cpe:2.3:a:elastic:kibana:*:*:*:*:*:*:*:* and centers on the Fleet/agent-policy subsystem rather than core Kibana UI.

RemediationAI

Vendor-released patch: upgrade Kibana to 8.19.16, 9.3.5, or 9.4.2 (or later) per Elastic advisory ESA-2026-38 at https://discuss.elastic.co/t/kibana-fleet-8-19-16-9-3-5-and-9-4-2-security-update-esa-2026-38/386559, which is the only complete fix because the issue lives in server-side validation of agent policy overrides. Until patched, compensating controls are to tightly restrict assignment of the Fleet management role (e.g. the built-in 'fleet_all' and equivalent custom roles) to a small, trusted operator group, audit recent agent policy changes and any newly issued Elastic Agent API keys for unexpected Elasticsearch privileges, and rotate Fleet-issued API keys after upgrade; the trade-off is operational overhead and brief agent re-enrollment churn. As an additional hardening step, separate the Kibana Fleet instance from the Elasticsearch cluster that hosts production security indices where feasible, accepting the cost of running a dedicated Fleet stack.