CVE-2026-49091
Received Received - Intake

Log Injection in Kibana via Terminal Control Sequences

Publication date: 2026-07-01

Last updated on: 2026-07-01

Assigner: Elastic

Description
Improper Output Neutralization for Logs (CWE-117) in Kibana can lead to log injection via Log Injection-Tampering-Forging (CAPEC-93). An attacker can supply specially crafted input that is written to log files without proper neutralization. When the log files are subsequently viewed in a terminal that interprets control sequences, the injected content may alter the displayed log data.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-01
Last Modified
2026-07-01
Generated
2026-07-02
AI Q&A
2026-07-01
EPSS Evaluated
N/A
NVD
CVE-2026-49091
EUVD
EUVD-2026-41101

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
elastic kibana to 7.17.15 (exc)
elastic kibana From 8.0.0 (inc) to 8.11.0 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-116 The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-49091 is a vulnerability in Kibana where specially crafted input is logged without proper neutralization, known as Improper Output Neutralization for Logs (CWE-117). This allows an attacker to perform log injection, where malicious content is inserted into log files.

When these manipulated log files are viewed in terminals that interpret control sequences, the injected content can alter how the log data is displayed, potentially misleading users or hiding malicious activity.

Compliance Impact

The provided information does not specify how this vulnerability affects compliance with common standards and regulations such as GDPR or HIPAA.

Impact Analysis

This vulnerability can impact you by allowing attackers to inject malicious content into Kibana log files. When these logs are viewed in certain terminals, the displayed log data can be manipulated.

  • Misleading or falsified log information could hide malicious activities or errors.
  • It may cause confusion or incorrect interpretation of log data by administrators or security personnel.
  • Potentially, it could be used to forge log entries, complicating incident response and forensic investigations.
Detection Guidance

This vulnerability involves specially crafted input being written to Kibana log files without proper neutralization, which can be detected by inspecting the log files for suspicious control sequences or unusual characters that may indicate log injection.

To detect this on your system, you can search Kibana log files for unexpected escape sequences or control characters that could be used for log injection.

  • Use grep or similar tools to search for escape sequences in log files, for example: grep -P '\x1b\[' /path/to/kibana/logs/*
  • Manually review recent Kibana log entries for any suspicious or malformed entries that include terminal control characters.
Mitigation Strategies

The primary mitigation step is to upgrade Kibana to versions 7.17.15 or 8.11.1 or later, where this vulnerability has been fixed.

If upgrading immediately is not possible, it is recommended to view Kibana log files only in tools that do not interpret terminal control sequences to avoid manipulation of displayed log data.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-49091. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart