Kibana Fleet vulnerabilities

Observable Discrepancy in Kibana Fleet leads to information disclosure. Fleet removes the Elasticsearch API key value from agent listing responses, but accepts caller-supplied filters evaluated with Kibana's internal privileges, creating a side channel to reconstruct the full API key.

Improper Privilege Management (CWE-269) in Kibana Fleet can lead to privilege escalation via Privilege Escalation (CAPEC-233). An integration policy may optionally declare extra data streams that the integration writes to, which Fleet adds to the Elasticsearch API key issued to Elastic Agents enrolled in the corresponding agent policy. The resulting key allows new documents to be inserted and index mappings to be extended for specific indices. The key does not allow reading, updating, or deleting existing documents.

Incorrect Authorization in Kibana Fleet can lead to privilege escalation. Fleet restricts some callers to managing integration policies for one specific integration, but when updating a policy, the restriction is evaluated against the stored integration rather than the replacement integration.