CVE-2025-20324VulnerabilityPublished 7 Jul 2025

CVE-2025-20324: 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 5.4 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.4Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 20% 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:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
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: 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: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 7 Jul 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 2026-10-26.

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 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.4 =9.3 =9.2 =9.1	Fixed in–

AI-suggested

European organizations should prioritize upgrading affected Splunk Enterprise and Cloud Platform instances to the fixed versions (9.4.2 or later for Enterprise, and corresponding Cloud Platform versions) as soon as possible. In the interim, organizations should audit and restrict access to Splunk roles, ensuring that low-privileged users do not have unnecessary access to the management REST API endpoints. Implement strict role-based access controls (RBAC) and monitor API usage for anomalous requests targeting `/servicesNS/nobody/search/admin/sourcetypes/`. Employ network segmentation and firewall rules to limit access to the Splunk management port to trusted administrators and systems only. Additionally, enable and review Splunk audit logs to detect unauthorized configuration changes. Conduct regular reviews of source type configurations to identify unexpected modifications. Incorporate this vulnerability into incident response plans and threat hunting activities to detect potential exploitation attempts. Finally, maintain up-to-date vulnerability management processes to track and apply vendor patches promptly.

Description

In Splunk Enterprise versions below 9.4.2, 9.3.5, 9.2.7, and 9.1.10 and Splunk Cloud Platform versions below 9.3.2411.104, 9.3.2408.113, and 9.2.2406.119, a low-privileged user that does not hold the "admin" or "power" Splunk roles could create or overwrite [system source type](https://help.splunk.com/en/splunk-enterprise/get-started/get-data-in/9.2/configure-source-types/create-source-types) configurations by sending a specially-crafted payload to the `/servicesNS/nobody/search/admin/sourcetypes/` REST endpoint on the Splunk management port.

Impact

For European organizations, this vulnerability poses a risk to the integrity and reliability of security monitoring and log management systems. Splunk is widely used in Europe for security information and event management (SIEM), compliance reporting, and operational intelligence. Unauthorized modification of source type configurations could allow attackers to evade detection by altering how logs are parsed or to inject misleading data, undermining incident response and compliance efforts (e.g., GDPR audit requirements). The confidentiality impact is limited but still relevant if sensitive log data is exposed or manipulated. The vulnerability could also disrupt operational processes dependent on accurate data ingestion. Organizations in regulated sectors such as finance, healthcare, and critical infrastructure in Europe could face increased risk of undetected breaches or compliance violations. Although exploitation requires some level of authenticated access, insider threats or compromised low-privileged accounts could leverage this vulnerability to escalate the impact of their activities. The absence of known exploits suggests a window of opportunity for defenders to patch and harden systems before active attacks emerge.

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Jul 2025, 21:38 UTC

Technical details

References

Community reviews

Related threats