# CVE-2019-7618: Path traversal in Elastic Code

> Attackers can read arbitrary local files from the Kibana instance by importing a malicious code repository into Elastic Code.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Oct 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-5xg9-ffw5-5c9c

## What is CVE-2019-7618?

CVE-2019-7618 is a medium-severity path traversal vulnerability in Elastic Kibana, published on 1 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A local file disclosure flaw was found in Elastic Code versions 7.3.0, 7.3.1, and 7.3.2. If a malicious code repository is imported into Code it is possible to read arbitrary files from the local filesystem of the Kibana instance running Code with the permission of the Kibana system user.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-538 (Insertion of Sensitive Information into Externally-Accessible File or Directory)

## Which versions are affected by CVE-2019-7618?

It affects 1 product.


Products: Elastic Kibana.

## How do I fix CVE-2019-7618?

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

## Is CVE-2019-7618 being exploited?

There is no known exploitation of CVE-2019-7618 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-2019-7618 and fix it if it is affected.

What it is: CVE-2019-7618 is a medium-severity path traversal vulnerability in Elastic Kibana, published on 1 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-7618 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-2019-7618/ (Markdown: https://insights.sbomify.com/CVE-2019-7618/index.md)
```

## Sources

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

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