How severe is CVE-2023-31422?

CVE-2023-31422 has a CVSS 3.x base score of 9.0, rated critical severity. It is exploitable over an adjacent network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2023-31422 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (47th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2023-31422?

CVE-2023-31422 affects Elastic Kibana. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2023-31422?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2023-31422 published?

CVE-2023-31422 was published on 2023-10-26 and last updated on 2026-06-17.

CVE-2023-31422

CVE-2023-31422 is a critical-severity vulnerability in Elastic Kibana with a CVSS 3.x base score of 9.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-532.

Key facts

Severity: Critical (CVSS 3.x base score 9.0)
EPSS exploit prediction: 1% (47th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-532
Affected product: Elastic Kibana
Published: 2023-10-26
Last modified: 2026-06-17

Description

An issue was discovered by Elastic whereby sensitive information is recorded in Kibana logs in the event of an error. The issue impacts only Kibana version 8.10.0 when logging in the JSON layout or when the pattern layout is configured to log the %meta pattern. Elastic has released Kibana 8.10.1 which resolves this issue. The error object recorded in the log contains request information, which can include sensitive data, such as authentication credentials, cookies, authorization headers, query params, request paths, and other metadata. Some examples of sensitive data which can be included in the logs are account credentials for kibana_system, kibana-metricbeat, or Kibana end-users.

Frequently asked questions

What is CVE-2023-31422?: An issue was discovered by Elastic whereby sensitive information is recorded in Kibana logs in the event of an error. The issue impacts only Kibana version 8.10.0 when logging in the JSON layout or when the pattern layout is configured to log the %meta pattern. Elastic has released Kibana 8.10.1 which resolves this issue. The error object recorded in the log contains request information, which can include sensitive data, such as authentication credentials, cookies, authorization headers, query params, request paths, and other metadata. Some examples of sensitive data which can be included in the logs are account credentials for kibana_system, kibana-metricbeat, or Kibana end-users.
How severe is CVE-2023-31422?: CVE-2023-31422 has a CVSS 3.x base score of 9.0, rated critical severity. It is exploitable over an adjacent network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2023-31422 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (47th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2023-31422?: CVE-2023-31422 affects Elastic Kibana. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2023-31422?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2023-31422 published?: CVE-2023-31422 was published on 2023-10-26 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:elastic:kibana:8.10.0:*:*:*:*:*:*:*

More vulnerabilities in Elastic Kibana

CVE-2019-7609 — Critical (CVSS 10.0): Kibana versions before 5.6.15 and 6.6.1 contain an arbitrary code execution flaw in the Timelion visualizer. An…
CVE-2025-25015 — Critical (CVSS 9.9): Prototype pollution in Kibana leads to arbitrary code execution via a crafted file upload and specifically crafted HTTP…
CVE-2024-37288 — Critical (CVSS 9.9): A deserialization issue in Kibana can lead to arbitrary code execution when Kibana attempts to parse a YAML document…
CVE-2018-17246 — Critical (CVSS 9.8): Kibana versions before 6.4.3 and 5.6.13 contain an arbitrary file inclusion flaw in the Console plugin. An attacker…
CVE-2018-17245 — Critical (CVSS 9.8): Kibana versions 4.0 to 4.6, 5.0 to 5.6.12, and 6.0 to 6.4.2 contain an error in the way authorization credentials are…
CVE-2025-25014 — Critical (CVSS 9.1): A Prototype pollution vulnerability in Kibana leads to arbitrary code execution via crafted HTTP requests to machine…

All CVEs affecting Elastic Kibana →

Other CWE-532 (Insertion of Sensitive Information into Log File) vulnerabilities

CVE-2022-36407 — Critical (CVSS 9.9): Insertion of Sensitive Information into Log File vulnerability in Hitachi Virtual Storage Platform, Hitachi Virtual…
CVE-2023-40029 — Critical (CVSS 9.9): Argo CD is a declarative continuous deployment for Kubernetes. Argo CD Cluster secrets might be managed declaratively…
CVE-2021-32724 — Critical (CVSS 9.9): check-spelling is a github action which provides CI spell checking. In affected versions and for a repository with the…
CVE-2026-49200 — Critical (CVSS 9.8): The acer_cgi.log file in the device firmware is accessible without authentication via the web interface. This file…
CVE-2026-22778 — Critical (CVSS 9.8): vLLM is an inference and serving engine for large language models (LLMs). From 0.8.3 to before 0.14.1, when an invalid…
CVE-2025-11008 — Critical (CVSS 9.8): The CE21 Suite plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and…

Browse all CWE-532 (Insertion of Sensitive Information into Log File) vulnerabilities →