CVE-2024-36991

HIGHNVD 7.59.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 94% probability of exploitation within the next 30 days (top 0.2% of all CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Elevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 13%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
9.0(high)
EPSS
95.9%
KEV
Not listed

Published

July 1, 2024

Last Modified

November 21, 2024

References (4)

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 39× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:26 UTCEPSS rescore
  2. 2026-07-11 08:26 UTCEPSS rescore
  3. 2026-07-09 19:09 UTCEPSS rescore
  4. 2026-07-08 15:14 UTCEPSS rescore
  5. 2026-07-08 15:13 UTCEPSS rescore
  6. 2026-07-07 13:45 UTCEPSS rescore
  7. 2026-07-06 16:26 UTCEPSS rescore
  8. 2026-07-06 02:22 UTCEPSS rescore
  9. 2026-07-06 02:22 UTCEPSS rescore
  10. 2026-07-05 02:29 UTCEPSS rescore
  11. 2026-07-04 06:30 UTCEPSS rescore
  12. 2026-07-01 15:05 UTCEPSS rescore
  13. 2026-06-30 23:21 UTCEPSS rescore
  14. 2026-06-30 23:21 UTCEPSS rescore
  15. 2026-06-29 14:05 UTCEPSS rescore
  16. 2026-06-28 14:06 UTCEPSS rescore
  17. 2026-06-28 14:06 UTCEPSS rescore
  18. 2026-06-28 04:55 UTCEPSS rescore
  19. 2026-06-28 04:55 UTCEPSS rescore
  20. 2026-06-27 03:07 UTCEPSS rescore
  21. 2026-06-27 03:07 UTCEPSS rescore
  22. 2026-06-25 13:49 UTCEPSS rescore
  23. 2026-06-24 14:04 UTCEPSS rescore
  24. 2026-06-24 14:04 UTCEPSS rescore
  25. 2026-06-23 21:32 UTCEPSS rescore
Show 30 more
  1. 2026-06-23 21:32 UTCEPSS rescore
  2. 2026-06-22 14:25 UTCEPSS rescore
  3. 2026-06-22 14:25 UTCEPSS rescore
  4. 2026-06-21 01:58 UTCEPSS rescore
  5. 2026-06-21 01:58 UTCEPSS rescore
  6. 2026-06-19 19:25 UTCEPSS rescore
  7. 2026-06-19 19:25 UTCEPSS rescore
  8. 2026-06-18 17:52 UTCEPSS rescore
  9. 2026-06-18 17:51 UTCEPSS rescore
  10. 2026-06-17 17:52 UTCEPSS rescore
  11. 2026-06-16 17:52 UTCEPSS rescore
  12. 2026-06-16 17:52 UTCEPSS rescore
  13. 2026-06-15 17:47 UTCEPSS rescore
  14. 2026-06-12 23:11 UTCEPSS rescore
  15. 2026-06-11 13:59 UTCEPSS rescore
  16. 2026-06-10 13:21 UTCEPSS rescore
  17. 2026-06-08 14:16 UTCEPSS rescore
  18. 2026-06-07 15:24 UTCEPSS rescore
  19. 2026-06-07 15:24 UTCEPSS rescore
  20. 2026-06-05 22:46 UTCEPSS rescore
  21. 2026-06-05 22:46 UTCEPSS rescore
  22. 2026-06-05 06:09 UTCEPSS rescore
  23. 2026-06-05 06:09 UTCEPSS rescore
  24. 2026-06-04 13:11 UTCEPSS rescore
  25. 2026-06-04 13:11 UTCEPSS rescore
  26. 2026-05-29 13:43 UTCEPSS rescore
  27. 2026-05-26 13:43 UTCEPSS rescore
  28. 2026-05-26 13:43 UTCEPSS rescore
  29. 2026-05-23 23:06 UTCEG score recompute
  30. 2026-05-23 23:06 UTCGHSA enrichment

Publicly available exploits

(10 references)

Working exploit code is in the public domain (9 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoC0xFZin/CVE-2024-36991
    First seen Jul 6, 2025

    Exploit for CVE-2024-36991 , written by me, enumerates a handfull of things, not all, cause not needed.

    Open source ↗
  • GitHub PoCgunzf0x/CVE-2024-36991
    First seen Mar 31, 2025

    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.

    Open source ↗
  • GitHub PoCTheStingR/CVE-2024-36991-Tool
    First seen Mar 30, 2025

    This binary POC automates the exploitation of CVE-2024-36991 by sending crafted curl requests to a vulnerable Splunk instance. It retrieves sensitive files and saves them locally for further analysis. The script is modular, allowing users to target specific file categories (e.g., credentials, logs, configurations).

    Open source ↗
  • GitHub PoCjaytiwari05/CVE-2024-36991
    First seen Mar 30, 2025

    Critical Splunk Vulnerability CVE-2024-36991: Patch Now to Prevent Arbitrary File Reads

    Open source ↗
  • GitHub PoCCappricio-Securities/CVE-2024-36991
    First seen Jul 10, 2024

    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.

    Open source ↗
  • GitHub PoCMr-xn/CVE-2024-36991
    First seen Jul 6, 2024

    Path Traversal On The "/Modules/Messaging/" Endpoint In Splunk Enterprise On Windows

    Open source ↗
  • GitHub PoCth3gokul/CVE-2024-36991
    First seen Jul 6, 2024

    CVE-2024-36991: Path traversal that affects Splunk Enterprise on Windows versions below 9.2.2, 9.1.5, and 9.0.10.

    Open source ↗
  • GitHub PoCsardine-web/CVE-2024-36991
    First seen Jul 6, 2024

    Path traversal vulnerability in Splunk Enterprise on Windows

    Open source ↗
  • GitHub PoCbigb0x/CVE-2024-36991
    First seen Jul 6, 2024

    POC for CVE-2024-36991: This exploit will attempt to read Splunk /etc/passwd file.

    Open source ↗
  • Nucleihttp/cves/2024/CVE-2024-36991.yaml
    First seen Jan 1, 2024

    Splunk Enterprise - Local File Inclusion

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-36991?
CVE-2024-36991 is a high vulnerability published on July 1, 2024. 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.
When was CVE-2024-36991 disclosed?
CVE-2024-36991 was first published in the National Vulnerability Database on July 1, 2024, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-36991 actively exploited?
CVE-2024-36991 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 95.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-36991?
CVE-2024-36991 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2024-36991?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-36991, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-36991

Explore →

Is Your Infrastructure Affected by CVE-2024-36991?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs