# CVE-2024-14047: Path traversal in Elastic Security

> A local attacker can exploit improper link resolution in the Winlogbeat installer to write or delete arbitrary files, causing denial of service.

- **Severity:** High 7.2 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:N/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Sep 2026
- **Updated:** 1 Sep 2026
- **Also known as:** GHSA-53p5-cgq8-8jm6

## What is CVE-2024-14047?

CVE-2024-14047 is a high-severity path traversal vulnerability in Elastic Security, published on 1 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A local vulnerability in the Winlogbeat Windows installer caused runtime files to be placed in a directory writable by unprivileged users. A low-privileged attacker with existing access to the system could pre-position malicious filesystem links, causing a subsequent elevated Winlogbeat operation to write to or delete arbitrary files. Successful exploitation could result in a denial of service.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2024-14047?

It affects 1 product.


Products: Elastic Winlogbeat.

## How do I fix CVE-2024-14047?

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

## Is CVE-2024-14047 being exploited?

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

## Other vulnerabilities in Elastic Security

- [CVE-2019-7613](https://insights.sbomify.com/CVE-2019-7613/): Winlogbeat versions before 5.6.16 and 6.6.2 had an insufficient logging flaw. (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-14047 and fix it if it is affected.

What it is: CVE-2024-14047 is a high-severity path traversal vulnerability in Elastic Security, published on 1 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-14047 in the wild and no public exploit code.

Affected product: Elastic Security. 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-2024-14047/ (Markdown: https://insights.sbomify.com/CVE-2024-14047/index.md)
```

## Sources

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

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