# CVE-2024-36991: Path Traversal on the “/modules/messaging/“ endpoint in Splunk Enterprise on Windows

> An attacker can perform path traversal on the messaging endpoint in Splunk Enterprise on Windows, potentially accessing or modifying files.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jul 2024
- **Updated:** 28 Feb 2025
- **Also known as:** GHSA-fg59-j242-rcj9

## What is CVE-2024-36991?

CVE-2024-36991 is a high-severity path traversal vulnerability in Splunk Splunk, published on 1 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Splunk Enterprise on Windows versions below 9.2.2, 9.1.5, and 9.0.10, an attacker could perform a path traversal on the /modules/messaging/ endpoint in Splunk Enterprise on Windows. This vulnerability should only affect Splunk Enterprise on Windows.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-35 (Path Traversal: '.../...//')

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

It affects 1 product.


Products: Splunk Splunk.

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

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

## Is CVE-2024-36991 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-36991 exists.

Public exploit code:

- POC for CVE-2024-36991: This exploit will attempt to read Splunk /etc/passwd file. (github_poc): https://github.com/bigb0x/CVE-2024-36991
- Path Traversal On The "/Modules/Messaging/" Endpoint In Splunk Enterprise On Windows (github_poc): https://github.com/Mr-xn/CVE-2024-36991
- Critical Splunk Vulnerability CVE-2024-36991: Patch Now to Prevent Arbitrary File Reads (github_poc): https://github.com/jaytiwari05/CVE-2024-36991
- Proof of Concept for CVE-2024-36991. Path traversal for Splunk versions below 9.2.2, 9.1.5, and 9.0.10 for Windows which allows arbitrary file read. (github_poc): https://github.com/gunzf0x/CVE-2024-36991
- Path traversal vulnerability in Splunk Enterprise on Windows versions below 9.2.2, 9.1.5, and 9.0.10 that allows reading sensitive files. (github_poc): https://github.com/Cappricio-Securities/CVE-2024-36991
- Exploit for CVE-2024-36991 , written by me, enumerates a handfull of things, not all, cause not needed. (github_poc): https://github.com/0xFZin/CVE-2024-36991

## Other vulnerabilities in Splunk Splunk

- [CVE-2026-20253](https://insights.sbomify.com/CVE-2026-20253/): Splunk Enterprise Missing Authentication for Critical Function (critical 9.8, exploited in the wild)
- [CVE-2026-76268](https://insights.sbomify.com/CVE-2026-76268/): Missing Authentication for Critical Function in the Patroni REST API in Splunk Enterprise (critical 9.8)
- [CVE-2026-76284](https://insights.sbomify.com/CVE-2026-76284/): Improper Neutralization in Splunk Enterprise (critical 9.8)
- [CVE-2026-76285](https://insights.sbomify.com/CVE-2026-76285/): Improper Adherence to Coding Standards in Splunk Enterprise (critical 9.8)
- [CVE-2017-17067](https://insights.sbomify.com/CVE-2017-17067/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-36991 is a high-severity path traversal vulnerability in Splunk Splunk, published on 1 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-36991 exists.

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

## Sources

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

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