CVE-2016-1000219: Kibana before 4.5.4 and 4.1.11 when a custom output is configured for logging in, cookies and authorization...

Security readout for executives and security teams

This issue could cause older Kibana deployments to write users' cookies and authorization headers into log files when custom logging output is configured. If someone can read those logs, they may be able to take over another user's Kibana session, especially behind authentication such as Shield. Exposure is likely limited to older Kibana 4.x deployments using custom logging output and authentication. Systems without affected versions, without custom logging output, or without accessible logs are less likely to be exposed based on the supplied sources. Treat this as a targeted information exposure risk, not a broad remote code execution emergency. Prioritize if legacy Kibana is still in use, logs are widely accessible, or authentication protects sensitive operational data. Mitigation focus: Upgrade Kibana to 4.5.4, 4.1.11, or a later supported release.; Review Elastic security guidance for version-specific remediation details.; Disable or reconfigure custom logging output that records sensitive headers..

Prepared

Jun 13, 2026, 04:43 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.