Skip to content
Fencer Intel
high 7.2

CVE-2026-49095 json

Improper Input Validation in Kibana Fleet Leading to Privilege Escalation

published 5mo ago modified 2mo ago also BIT-elk-2026-49095 , BIT-kibana-2026-49095 , EUVD-2026-33033

cvss
7.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 18%
public exploits
0
none known

Summary

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.

Patch / fix

  • bitnami elk 8.19.16, 9.3.5, 9.4.2
  • bitnami kibana 8.19.16, 9.3.5, 9.4.2
  • elastic kibana 8.19.16, 9.3.5, 9.4.2
  • elasticsearch kibana 8.19.16, 9.3.5, 9.4.2

Is CVE-2026-49095 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
5mo ago

Exploit prediction

0.26% chance of exploitation in the next 30 days, higher than 18% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
OSV 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
bitnami elk
>=8.0.0, <8.19.16
>=9.0.0, <9.3.5
>=9.4.0, <9.4.2
8.19.16
9.3.5
9.4.2
bitnami kibana
>=8.0.0, <8.19.16
>=9.0.0, <9.3.5
>=9.4.0, <9.4.2
8.19.16
9.3.5
9.4.2

Affected products

  • Elastic Kibana

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.