# CVE-2026-49091: Elastic Kibana log injection in log output

Source: https://junglewise.ai/threats/cve-2026-49091-elastic-kibana-log-injection-in-log-output  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-07-01. Updated: 2026-07-01  
License: CC BY 4.0 with a link back

CVE-2026-49091 · Severity: high · CVSS 8 · Published 2026-07-01

Kibana, a popular data visualization and management platform for the Elastic Stack, is vulnerable to a log injection flaw. An attacker can provide malicious input that, when recorded in system logs, can manipulate how those logs appear to administrators viewing them in a command-line terminal. This could allow an attacker to hide their activities or forge log entries, potentially misleading security investigations or operational monitoring.

Technologies: [Elastic Kibana](https://junglewise.ai/threats/technologies/kibana). Vendors: [Elastic](https://junglewise.ai/threats/vendors/elastic).

## Quick answers

**Is CVE-2026-49091 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-49091 being exploited in the wild.

**How severe is CVE-2026-49091?** High severity, with a CVSS score of 8, published 1 July 2026.

**Which products and versions are affected?** Elastic Kibana 7.0.0 to 7.17.14, 8.0.0 to 8.11.0.

**Is there a fix for CVE-2026-49091?** A patch was published on 2026-07-01. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-49091 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-49091?** Check whether you run Elastic Kibana at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

A log injection vulnerability exists in Kibana due to improper neutralization of output for logs (CWE-117). An authenticated attacker with network access can supply specially crafted input containing terminal control sequences. When these sequences are written to log files and subsequently viewed in a terminal that interprets such sequences, the attacker can alter the displayed log data (CAPEC-93). This can be used to forge log entries or hide malicious activity. The vulnerability is mitigated if logs are viewed in tools that do not interpret terminal control sequences. Patches are available in versions 7.17.15 and 8.11.1.

## Affected products

- Elastic Kibana 7.0.0 to 7.17.14, 8.0.0 to 8.11.0

## Timeline

- 2026-07-01: disclosed
- 2026-07-01: advisory
- 2026-07-01: patched

## References

- [https://discuss.elastic.co/t/kibana-7-17-15-8-11-1-security-update-esa-2026-53](https://discuss.elastic.co/t/kibana-7-17-15-8-11-1-security-update-esa-2026-53)

## Related threats

- [Elastic Kibana authorization bypass in connector logs](https://junglewise.ai/threats/cve-2026-115295-authorization-bypass-through-user-controlled-key-cwe-639-in)
- [Elastic Kibana path traversal in Fleet feature](https://junglewise.ai/threats/cve-2026-115294-improper-limitation-of-a-pathname-to-a-restricted-directory-cwe)
- [Elastic Kibana credential disclosure in Observability onboarding](https://junglewise.ai/threats/cve-2026-115293-insertion-of-sensitive-information-into-sent-data-cwe-201-in)
- [Elastic Kibana authorization bypass in Machine Learning](https://junglewise.ai/threats/cve-2026-115292-authorization-bypass-through-user-controlled-key-cwe-639-in)
- [Elastic Kibana incorrect authorization in Fleet settings](https://junglewise.ai/threats/cve-2026-102412-incorrect-authorization-cwe-863-in-kibana-can-lead-to-sensitive)