Kibana Fleet EUVD-2026-70657

Exploitation requires a valid Kibana account with the Fleet management role (or equivalent privilege to create or modify integration packages and Fleet policies). The target environment must be running Elastic Fleet with at least one active agent policy and enrolled Elastic Agents - deployments using Kibana solely for dashboarding without Fleet are not affected. No special network position is required beyond authenticated access to the Kibana API (AV:N/AC:L). Exploitation is limited by the Fleet management privilege requirement: anonymous users and low-privilege read-only Kibana users cannot trigger the flaw. Environments that restrict Fleet management to a small set of tightly controlled service accounts face significantly lower practical risk.

The vendor-provided CVSS score of 8.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N) captures the core metrics well, but the S:U (unchanged scope) designation is arguable: the attack originates in Kibana's Fleet component yet delivers its impact by elevating credentials used against a distinct system - the Elasticsearch cluster - and all enrolled Elastic Agents. A case for S:C exists, which would push the score above 9.0. EPSS data is not provided; given the authenticated requirement (PR:L, Fleet management role) and the specificity of the Elastic Fleet deployment model, opportunistic mass exploitation is unlikely. However, in environments where Fleet management is distributed to multiple operators or service accounts, any one of those accounts represents an exploitation path. No public exploit code and no CISA KEV confirmation at time of analysis. Real-world risk is meaningful in enterprise Elastic Stack environments where Elastic Agents are widely deployed across endpoints or cloud workloads - compromise of agent credentials can enable silent data exfiltration or cluster manipulation. The availability of a vendor patch (ESA-2026-140) reduces residual risk for patched installations.

An adversary who has compromised or legitimately holds a Fleet management account in Kibana crafts or modifies an integration package to declare full Elasticsearch cluster administration privileges. They apply this package to a Fleet policy and save it without triggering any server-side validation. Kibana then generates new API keys for every Elastic Agent enrolled in that policy, each key carrying cluster:admin scope; the agents begin authenticating to Elasticsearch with those elevated credentials, giving the adversary covert full cluster access through any of the now-overprivileged agents.