# CVE-2023-46675: Kibana Insertion of Sensitive Information into Log File

> Attackers with log access can read sensitive credentials and keys leaked in Kibana logs during errors or debug logging.

- **Severity:** High 8.0 (`CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Dec 2023
- **Updated:** 22 May 2025
- **Also known as:** GHSA-6g3x-hhx6-885v

## What is CVE-2023-46675?

CVE-2023-46675 is a high-severity vulnerability in Elastic Kibana, published on 13 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered by Elastic whereby sensitive information may be recorded in Kibana logs in the event of an error or in the event where debug level logging is enabled in Kibana. Elastic has released Kibana 8.11.2 which resolves this issue. The messages recorded in the log may contain Account credentials for the kibana_system user, API Keys, and credentials of Kibana end-users, Elastic Security package policy objects which can contain private keys, bearer token, and sessions of 3rd-party integrations and finally Authorization headers, client secrets, local file paths, and stack traces. The issue may occur in any Kibana instance running an affected version that could potentially receive an unexpected error when communicating to Elasticsearch causing it to include sensitive data into Kibana error logs. It could also occur under specific circumstances when debug level logging is enabled in Kibana. Note: It was found that the fix for ESA-2023-25 in Kibana 8.11.1 for a similar issue was incomplete.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2023-46675?

It affects 1 product.


Products: Elastic Kibana.

## How do I fix CVE-2023-46675?

No fix has been published for CVE-2023-46675 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-46675 being exploited?

There is no known exploitation of CVE-2023-46675 in the wild and no public exploit code.

## Other vulnerabilities in Elastic Kibana

- [CVE-2019-7609](https://insights.sbomify.com/CVE-2019-7609/): Kibana Arbitrary Code Execution (critical 9.8, exploited in the wild)
- [CVE-2025-25015](https://insights.sbomify.com/CVE-2025-25015/): Kibana arbitrary code execution via prototype pollution (critical 9.9)
- [CVE-2024-37288](https://insights.sbomify.com/CVE-2024-37288/): Deserialization in Kibana (critical 9.9)
- [CVE-2023-31415](https://insights.sbomify.com/CVE-2023-31415/): Code injection in Kibana (critical 9.9)
- [CVE-2018-17245](https://insights.sbomify.com/CVE-2018-17245/): Information disclosure in Kibana (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-46675 and fix it if it is affected.

What it is: CVE-2023-46675 is a high-severity vulnerability in Elastic Kibana, published on 13 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-46675 in the wild and no public exploit code.

Affected product: Elastic Kibana. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-46675/ (Markdown: https://insights.sbomify.com/CVE-2023-46675/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-46675
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-46675
- OSV: https://osv.dev/vulnerability/CVE-2023-46675

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-46675/
Summaries are generated and may contain mistakes; the official description above is the record.