CVE-2026-72631: CWE-269 Improper Privilege Management in Elastic Kibana
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
AI Analysis
Technical Summary
This vulnerability (CVE-2026-72631) in Elastic Kibana Fleet involves improper privilege management (CWE-269) where integration policies can declare additional data streams that are included in the Elasticsearch API key granted to Elastic Agents. The API key permits inserting new documents and extending index mappings on specific indices but restricts reading, updating, or deleting existing documents. This can lead to privilege escalation (CAPEC-233) by allowing agents to perform unauthorized data insertions and schema changes. The vulnerability affects Kibana versions 9.1.0 and 9.5.0. No official patch or remediation level has been provided yet, and there are no known exploits in the wild.
Potential Impact
The vulnerability allows privilege escalation by granting Elastic Agents API keys that permit insertion of new documents and extension of index mappings on certain indices. This could impact data integrity by allowing unauthorized data insertion and schema modification. However, the API key does not allow reading, updating, or deleting existing documents, limiting the scope of potential damage. The CVSS score of 6.5 reflects a medium severity impact primarily on data integrity.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official fix or remediation level is provided, users should monitor Elastic's advisories for updates. Until a fix is available, carefully review and restrict integration policies that declare extra data streams to minimize exposure. Avoid granting overly broad privileges in API keys issued to Elastic Agents.
CVE-2026-72631: CWE-269 Improper Privilege Management in Elastic Kibana
Description
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
CVSS v3.1
Score 6.5medium
Affected software
Elastic
Kibana
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability (CVE-2026-72631) in Elastic Kibana Fleet involves improper privilege management (CWE-269) where integration policies can declare additional data streams that are included in the Elasticsearch API key granted to Elastic Agents. The API key permits inserting new documents and extending index mappings on specific indices but restricts reading, updating, or deleting existing documents. This can lead to privilege escalation (CAPEC-233) by allowing agents to perform unauthorized data insertions and schema changes. The vulnerability affects Kibana versions 9.1.0 and 9.5.0. No official patch or remediation level has been provided yet, and there are no known exploits in the wild.
Potential Impact
The vulnerability allows privilege escalation by granting Elastic Agents API keys that permit insertion of new documents and extension of index mappings on certain indices. This could impact data integrity by allowing unauthorized data insertion and schema modification. However, the API key does not allow reading, updating, or deleting existing documents, limiting the scope of potential damage. The CVSS score of 6.5 reflects a medium severity impact primarily on data integrity.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official fix or remediation level is provided, users should monitor Elastic's advisories for updates. Until a fix is available, carefully review and restrict integration policies that declare extra data streams to minimize exposure. Avoid granting overly broad privileges in API keys issued to Elastic Agents.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- elastic
- Date Reserved
- 2026-08-10T11:17:29.887Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a7e1a7fbf8831d539b180e6
Added to database: 08/13/2026, 19:26:55 UTC
Last enriched: 08/13/2026, 20:12:55 UTC
Last updated: 09/27/2026, 13:47:47 UTC
Views: 39
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.