VulnerabilityPublished 1 Oct 2025

CVE-2025-20366: Splunk Enterprise · The software does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Affects Splunk EnterpriseSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 1 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Splunk Splunk Enterprise	Affected 9.2 – 10.0 4 affected builds	Fixed in–

AI-suggested

To mitigate CVE-2025-20366, European organizations should immediately upgrade affected Splunk Enterprise and Splunk Cloud Platform instances to versions 9.4.4, 9.3.6, 9.2.8 or later, as these contain the necessary access control fixes. Until upgrades can be applied, organizations should restrict access to the Splunk search job management interfaces and ensure that low-privileged users cannot enumerate or guess Search IDs (SIDs). Implement network segmentation and strict role-based access controls (RBAC) to limit which users can view or interact with search jobs. Monitoring and alerting on unusual access patterns to search job endpoints can help detect exploitation attempts. Additionally, review and audit Splunk user roles and permissions regularly to minimize the number of users with elevated privileges. If possible, disable or limit background administrative search jobs that produce sensitive results accessible via SIDs. Finally, educate administrators and security teams about this vulnerability and the importance of applying patches promptly.

Description

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.

Impact

For European organizations, the primary impact of CVE-2025-20366 is the unauthorized disclosure of sensitive information contained in Splunk search results. Since Splunk is widely used for security monitoring, log analysis, and operational intelligence, exposure of these results could reveal confidential operational data, security alerts, or personally identifiable information (PII). This could lead to compliance violations under GDPR and other data protection regulations, reputational damage, and increased risk of targeted attacks if threat intelligence or internal security posture details are leaked. The vulnerability does not allow modification or disruption of services, so integrity and availability impacts are minimal. However, the confidentiality breach alone can have serious consequences in sectors such as finance, telecommunications, government, and critical infrastructure, where Splunk is heavily deployed. The ease of exploitation (low privilege and no user interaction) increases the risk profile, especially in multi-tenant or shared environments where low-privileged users exist. Organizations that have not upgraded to patched versions remain vulnerable to potential insider threats or attackers who gain low-level access.

References

advisory.splunk.com/advisories/SVD-2025-1001 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Oct 2025, 16:57 UTC

Technical details

References

Community reviews

Related threats