How severe is CVE-2024-36996?

CVE-2024-36996 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.

Is CVE-2024-36996 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (27th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2024-36996?

CVE-2024-36996 primarily affects Splunk. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2024-36996?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2024-36996 have an EU (EUVD) identifier?

Yes. CVE-2024-36996 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-36383.

When was CVE-2024-36996 published?

CVE-2024-36996 was published on 2024-07-01 and last updated on 2026-06-17.

CVE-2024-36996

CVE-2024-36996 is a medium-severity vulnerability in Splunk with a CVSS 3.x base score of 5.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-203.

Key facts

Severity: Medium (CVSS 3.x base score 5.3)
EPSS exploit prediction: 0% (27th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2024-36383
Weakness: CWE-203
Affected product: Splunk
Published: 2024-07-01
Last modified: 2026-06-17

Description

In Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10 and Splunk Cloud Platform versions below 9.1.2312.109, an attacker could determine whether or not another user exists on the instance by deciphering the error response that they would likely receive from the instance when they attempt to log in. This disclosure could then lead to additional brute-force password-guessing attacks. This vulnerability would require that the Splunk platform instance uses the Security Assertion Markup Language (SAML) authentication scheme.

Frequently asked questions

What is CVE-2024-36996?: In Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10 and Splunk Cloud Platform versions below 9.1.2312.109, an attacker could determine whether or not another user exists on the instance by deciphering the error response that they would likely receive from the instance when they attempt to log in. This disclosure could then lead to additional brute-force password-guessing attacks. This vulnerability would require that the Splunk platform instance uses the Security Assertion Markup Language (SAML) authentication scheme.
How severe is CVE-2024-36996?: CVE-2024-36996 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2024-36996 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (27th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-36996?: CVE-2024-36996 primarily affects Splunk. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2024-36996?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2024-36996 have an EU (EUVD) identifier?: Yes. CVE-2024-36996 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-36383.
When was CVE-2024-36996 published?: CVE-2024-36996 was published on 2024-07-01 and last updated on 2026-06-17.

References

https://advisory.splunk.com/advisories/SVD-2024-0716

Affected products (2)

cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:*:*:*:*:*:*:*:*

More vulnerabilities in Splunk

CVE-2026-20253 — Critical (CVSS 9.8): In Splunk Enterprise 10.2 versions below 10.2.4 and 10 versions below 10.0.7, an unauthenticated user could create or…
CVE-2017-17067 — Critical (CVSS 9.8): Splunk Web in Splunk Enterprise 7.0.x before 7.0.0.1, 6.6.x before 6.6.3.2, 6.5.x before 6.5.6, 6.4.x before 6.4.9, and…
CVE-2016-10126 — Critical (CVSS 9.8): Splunk Web in Splunk Enterprise 5.0.x before 5.0.17, 6.0.x before 6.0.13, 6.1.x before 6.1.12, 6.2.x before 6.2.12,…
CVE-2013-6771 — Critical (CVSS 9.3): Directory traversal vulnerability in the collect script in Splunk before 5.0.5 allows remote attackers to execute…
CVE-2011-4644 — Critical (CVSS 9.3): Splunk 4.2.5 and earlier, when a Free license is selected, enables potentially undesirable functionality within an…
CVE-2022-32158 — Critical (CVSS 9.0): Splunk Enterprise deployment servers in versions before 8.1.10.1, 8.2.6.1, and 9.0 let clients deploy forwarder bundles…

All CVEs affecting Splunk →

Other CWE-203 (Observable Discrepancy) vulnerabilities

CVE-2019-25337 — Critical (CVSS 9.8): OwnCloud 8.1.8 contains a username enumeration vulnerability that allows remote attackers to discover user accounts by…
CVE-2026-23519 — Critical (CVSS 9.8): RustCrypto CMOV provides conditional move CPU intrinsics which are guaranteed on major platforms to execute in…
CVE-2025-27667 — Critical (CVSS 9.8): Vasion Print (formerly PrinterLogic) before Virtual Appliance Host 22.0.843 Application 20.0.1923 allows Administrative…
CVE-2024-25714 — Critical (CVSS 9.8): In Rhonabwy through 1.1.13, HMAC signature verification uses a strcmp function that is vulnerable to side-channel…
CVE-2024-25191 — Critical (CVSS 9.8): php-jwt 1.0.0 uses strcmp (which is not constant time) to verify authentication, which makes it easier to bypass…
CVE-2024-25190 — Critical (CVSS 9.8): l8w8jwt 2.2.1 uses memcmp (which is not constant time) to verify authentication, which makes it easier to bypass…

Browse all CWE-203 (Observable Discrepancy) vulnerabilities →