Skip to content
Noroxi
CVE-2025-20366· NVD / CVE Program· CNA cisco

Improper Access Control in Background Job Submission in Splunk Enterprise

In Splunk Enterprise versions below 9.4.4, 9.3.6, and 9.2.8, and Splunk Cloud Platform versions below 9.3.2411.111, 9.3.2408.119, and 9.2.2406.122, a low-privileged user that does not hold the admin or power Splunk roles could access sensitive search results if Splunk Enterprise runs an administrative search job in the background. If the low privileged user guesses the search job’s unique Search ID (SID), the user could retrieve the results of that job, potentially exposing sensitive search results. For more information see https://help.splunk.com/en/splunk-enterprise/search/search-manual/10.0/manage-jobs/about-jobs-and-job-management and https://help.splunk.com/en/splunk-enterprise/search/search-manual/10.0/manage-jobs/manage-search-jobs.

MediumCVSS 6.5 · v3.1—No exploit No fix recorded
Published
Oct 1, 2025
Updated
Jun 17, 2026
EPSS
0.4% · 36th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

26

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · cisco
6.5
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
splunksplunk
splunksplunk cloud platform

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • splunk splunk9.2.0 and later · before 9.2.8
  • splunk splunk9.3.0 and later · before 9.3.6
  • splunk splunk9.4.0 and later · before 9.4.4
  • splunk splunk cloud platform9.2.2406 and later · before 9.2.2406.122
  • splunk splunk cloud platform9.3.2408 and later · before 9.3.2408.119
  • splunk splunk cloud platform9.3.2411 and later · before 9.3.2411.111

Versions reported by the vendor

Affected version ranges reported by the assigning authority (cisco). Independent of NVD's CPE analysis and usually ahead of it.

  • Splunk Splunk Cloud Platform

    • 9.3.2411 and later · before 9.3.2411.111affected
    • 9.3.2408 and later · before 9.3.2408.119affected
    • 9.2.2406 and later · before 9.2.2406.122affected
  • Splunk Splunk Enterprise

    • 10.0 and later · before 10.0.0affected
    • 9.4 and later · before 9.4.4affected
    • 9.3 and later · before 9.3.6affected
    • 9.2 and later · before 9.2.8affected

Other highest-scoring records for the same primary product.

  • CVE-2026-20253Unauthenticated Arbitrary File Creation and Truncation in a PostgreSQL Sidecar Service Endpoint in Splunk EnterpriseKEV
    98Now
  • CVE-2023-32707‘edit_user’ Capability Privilege Escalation
    59Plan
  • CVE-2018-11409Splunk through 7.0.1 allows information disclosure by appending __raw/services/server/info/server-info?output_mode=json to a query, as demon
    50Plan
  • CVE-2026-20251Remote Code Execution through Deserialization of Untrusted Data in Splunk Secure Gateway
    45Plan
  • CVE-2023-32714Path Traversal in Splunk App for Lookup File Editing
    45Plan
  • CVE-2022-32158Splunk Enterprise deployment servers allow client publishing of forwarder bundles
    40Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2025-20229189 days apartRemote Code Execution through file upload to “$SPLUNK_HOME/var/run/splunk/apptemp“ directory in Splunk Enterprise
    37Monitor
  • CVE-2026-76310322 days apartImproper Access Control through Embedded Report REST API Requests in Splunk Enterprise
    37Monitor
  • CVE-2026-76311322 days apartImproper Access Control in Embedded Report Dispatch Archives in Splunk Enterprise
    37Monitor
  • CVE-2026-76312322 days apartImproper Access Control through Embedded Reports in Splunk Enterprise
    37Monitor
  • CVE-2026-76313322 days apartRemote Code Execution (RCE) through the REST API in Splunk Enterprise
    35Monitor
  • CVE-2025-20230189 days apartMissing Access Control and Incorrect Ownership of Data in App Key Value Store (KVStore) collections in the Splunk Secure Gateway App
    26Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

nvd-secondary

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records