VulnerabilityPublished 12 Nov 2025

CVE-2025-20379: Splunk Enterprise · The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Affects Splunk EnterpriseSource CVE Database V5

Not known to be exploited · CVSS 3.5 Low.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

3.5Low

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
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 12 Nov 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

European organizations should immediately upgrade affected Splunk Enterprise and Cloud Platform instances to the patched versions specified by Splunk (10.0.1, 9.4.5, 9.3.7, 9.2.9 for Enterprise and corresponding Cloud versions). In the interim, restrict access to the /services/streams/search endpoint to only trusted users and roles, and implement strict role-based access controls to ensure low-privileged users cannot execute saved searches with risky commands. Enhance phishing defenses through user training, email filtering, and multi-factor authentication to reduce the risk of attackers tricking users into initiating malicious requests. Monitor Splunk logs for unusual activity related to saved searches and REST API calls, especially those involving the 'q' parameter. Consider implementing web application firewalls or API gateways that can detect and block suspicious character encoding or anomalous REST requests. Regularly audit Splunk roles and permissions to minimize privilege creep and ensure that only necessary users have elevated roles. Finally, maintain an incident response plan that includes detection and containment strategies for potential exploitation attempts.

Description

In Splunk Enterprise versions below 10.0.1, 9.4.5, 9.3.7, and 9.2.9 and Splunk Cloud Platform versions below 9.3.2411.116, 9.3.2408.124, 10.0.2503.5 and 10.1.2507.1, a low-privileged user that does not hold the “admin“ or “power“ Splunk roles could run a saved search with a risky command using the permissions of a higher-privileged user to bypass the SPL safeguards for risky commands. They could bypass these safeguards on the “/services/streams/search“ endpoint through its “q“ parameter by circumventing endpoint restrictions using character encoding in the REST path. The vulnerability requires the attacker to phish the victim by tricking them into initiating a request within their browser. The authenticated user should not be able to exploit the vulnerability at will.

Impact

For European organizations, the primary impact is unauthorized disclosure of sensitive information within Splunk environments, which may include logs, monitoring data, or other operational intelligence. This could lead to exposure of confidential business information, compliance violations (e.g., GDPR), and potential reputational damage. Since Splunk is widely used in sectors such as finance, telecommunications, and critical infrastructure monitoring across Europe, unauthorized access to sensitive data could aid attackers in reconnaissance or lateral movement. The requirement for phishing and user interaction reduces the likelihood of widespread automated exploitation but increases risk in organizations with less mature security awareness or phishing defenses. The vulnerability does not allow data modification or service disruption, limiting direct operational impact but still posing a significant confidentiality risk. Organizations handling regulated or sensitive data must consider this vulnerability a threat to data privacy and compliance obligations.

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Nov 2025, 19:04 UTC

Technical details

References

Community reviews

Related threats