Splunk vulnerabilities1 known to be exploited.

Vendor1 known exploited
The short answer

Splunk has 238 published vulnerabilities across 15 products in our catalogue. 1 of them is on the list of flaws known to be exploited, so criminals are using them now. The most affected product is Splunk, with 166. If you run Splunk software, patch the exploited flaws first.

See the exploited flaws

The most recent Splunk flaw added to the known-exploited list is CVE-2014-0160, on 4 May 2022. We keep watching the known-exploited list.

Products

Which Splunk products have the most vulnerabilities?

Splunk leads with 166 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.

Known exploited

Which Splunk vulnerabilities are being exploited?

1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.

  1. 7.5
    CVE-2014-0160HighKnown exploited
    OpenSSL Information Disclosure Vulnerability

    The TLS and DTLS implementations in OpenSSL do not properly handle Heartbeat Extension packets, which allows remote attackers to obtain sensitive information.

    Chance of use>99%Known exploited since4 May 2022
Exploit likelihood

Which Splunk flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. >99%
    CVE-2014-0160HighKnown exploited

    The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows remote attackers to obtain sensitive information from process memory via...

    CVSS7.5Published7 Apr 2014
  2. 98%

    Splunk through 7.0.1 allows information disclosure by appending __raw/services/server/info/server-info?output_mode=json to a query, as demonstrated by discovering a license key.

    CVSS5.3Published8 Jun 2018
  3. 89%

    In Splunk Enterprise versions below 9.0.7 and 9.1.2, Splunk Enterprise does not safely sanitize extensible stylesheet language transformations (XSLT) that users supply.

    CVSS8.8Published16 Nov 2023
  4. 79%

    In versions of Splunk Enterprise below 9.0.5, 8.2.11, and 8.1.14, and Splunk Cloud Platform below version 9.0.2303.100, a low-privileged user who holds a role that has the ‘edit_user’ capability assigned to it can...

    CVSS8.8Published1 Jun 2023
  5. 64%

    curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when a TLS 1.3 session ticket arrives over a connection.

    CVSS8.1Published11 Jun 2021
  6. 43%

    In the Splunk App for Lookup File Editing versions below 4.0.1, a low-privileged user can, with a specially crafted web request, trigger a path traversal exploit that can then be used to read and write to restricted...

    CVSS8.1Published1 Jun 2023
  7. 43%

    In Splunk Enterprise versions below 8.1.12, 8.2.9, and 9.0.2, a View allows for a Reflected Cross Site Scripting via JavaScript Object Notation (JSON) in a query parameter when output_mode=radio.

    CVSS6.1Published4 Nov 2022
  8. 36%

    curl < 7.84.0 supports "chained" HTTP compression algorithms, meaning that a serverresponse can be compressed multiple times and potentially with different algorithms.

    CVSS6.5Published7 Jul 2022
  9. 31%

    A malicious server can serve excessive amounts of `Set-Cookie:` headers in a HTTP response to curl and curl < 7.84.0 stores all of them.

    CVSS4.3Published7 Jul 2022
  10. 29%

    In Splunk Enterprise versions below 9.4.2, 9.3.4 and 9.2.6, and Splunk Cloud Platform versions below 9.3.2411.102, 9.3.2408.111 and 9.2.2406.118, a low-privileged user that does not hold the "admin" or "power" Splunk...

    CVSS4.3Published2 Jun 2025
Precursor Intelligence

Running Splunk? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

Our catalogue lists 238 published vulnerabilities across 15 products and 461 versions from Splunk. The most recent Splunk flaw added to the known-exploited list is CVE-2014-0160, on 4 May 2022.

1 Splunk vulnerability is on the list of flaws known to be exploited. The most recently added is CVE-2014-0160. The full list is on this page.

Splunk, with 166 published vulnerabilities. Its own page lists the ones known to be exploited.

Create a Precursor Intelligence account and track the Splunk products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.