Security readout for executives and security teams
Plain-English summary
This Kibana Fleet flaw lets a highly privileged Fleet user abuse weak validation in agent policy overrides. If successful, Elastic Agents may receive API keys with broader Elasticsearch access than intended, including sensitive security indices. The main business concern is insider or compromised-admin expansion of access, not unauthenticated internet exploitation.
Executive priority
Treat as high priority for Elastic environments using Fleet, especially where many administrators or automation accounts can manage Fleet. The issue is privilege escalation after authentication, so urgency is driven by who has Fleet rights and whether those accounts are tightly controlled.
Technical view
CVE-2026-49095 is CWE-20 improper input validation in Kibana Fleet agent policy management. An authenticated user with Fleet management privileges can inject values into a configuration override mechanism, causing Elastic Agents to receive elevated Elasticsearch API key privileges. CVSS is 7.2, high, with high confidentiality and integrity impact and no availability impact.
Likely exposure
Exposure is limited to Elastic Kibana deployments using Fleet where users or service accounts have Fleet management privileges. The provided affected list names Elastic Kibana versions 8.0.0, 9.0.0, and 9.4.0, with default status otherwise unaffected; verify exact applicability against Elastic ESA-2026-38.
Exploitation context
The bundle does not cite active exploitation, and KEV status is false. Exploitation requires authentication and high privileges, but impact can be serious because the flaw may turn Fleet management rights into unauthorized read/write access to Elasticsearch security indices.
Researcher notes
The provided evidence identifies the vulnerable component, privilege requirement, impact path, CVSS, CWE, and Elastic advisory reference. It does not provide exploit details, proof of exploitation, or complete fixed-version mapping beyond the advisory title and affected-version entries, so validation should rely on Elastic's advisory and local role/API-key review.
Mitigation direction
- Review Elastic ESA-2026-38 for exact affected and fixed Kibana versions.
- Prioritize applying Elastic's Kibana Fleet security update where applicable.
- Restrict Fleet management privileges to trusted administrators only.
- Audit Fleet policy override usage for unexpected or unauthorized changes.
- Review Elastic Agent API key privileges after remediation.
Validation and detection
- Inventory Kibana versions and identify deployments using Fleet agent policy management.
- List users, roles, and service accounts with Fleet management privileges.
- Check Fleet agent policies for unexpected configuration override values.
- Review Elasticsearch API keys issued to Elastic Agents for excessive privileges.
- Confirm remediation status against Elastic ESA-2026-38 and CVE records.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-20: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-49095 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N1.25.2elasticVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://discuss.elastic.co/t/kibana-fleet-8-19-16-9-3-5-and-9-4-2-security-update-esa-2026-38/386559CVE reference, elastic
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.