VulnerabilityPublished 11 Mar 2026Updated 12 Mar 2026

CVE-2026-20166: Splunk Cloud Platform · Information Exposure

Affects Splunk Cloud PlatformSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.4 Medium · fixed in 10.2.1 : update Splunk Cloud Platform when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

5.4Medium

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 10.2.1, 10.0.4, 10.2.2510.5 +2

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 11 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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

Upgrade Splunk to 10.2.2510.5, 10.1.2507.16 or 10.0.2503.12 (Cloud Platform); 10.2.1 or 10.0.4 (Enterprise).

Affected software

Product	Affected	Fixed in
SplunkSplunk Enterprise	Affected >=10.2 <10.2.1	Fixed in 10.2.1
SplunkSplunk Enterprise	Affected >=10.0 <10.0.4	Fixed in 10.0.4
SplunkSplunk Cloud Platform	Affected >=10.2.2510 <10.2.2510.5	Fixed in 10.2.2510.5
SplunkSplunk Cloud Platform	Affected >=10.1.2507 <10.1.2507.16	Fixed in 10.1.2507.16
SplunkSplunk Cloud Platform	Affected >=10.0.2503 <10.0.2503.12	Fixed in 10.0.2503.12

AI-suggested

Organizations should upgrade affected Splunk Enterprise instances to version 10.2.1 or later and Splunk Cloud Platform to the fixed versions (10.2.2510.5, 10.1.2507.16, or 10.0.2503.12) as soon as possible. If you cannot patch yet, restrict access to the Discover Splunk Observability Cloud app to only trusted users with appropriate roles (admin or power roles). Review and tighten role-based access controls (RBAC) to ensure that low-privileged users cannot access sensitive applications or tokens. Monitor Splunk logs for unusual access patterns or token usage that could indicate exploitation attempts. Consider rotating the Observability Cloud API tokens after patching to invalidate any tokens potentially exposed. Additionally, implement network segmentation and least privilege principles to limit the exposure of Splunk management interfaces. Regularly audit Splunk configurations and installed apps to detect unauthorized changes or additions that could introduce similar risks.

Description

In Splunk Enterprise versions below 10.2.1 and 10.0.4, and Splunk Cloud Platform versions below 10.2.2510.5, 10.1.2507.16, and 10.0.2503.12, a low-privileged user that does not hold the "admin" or "power" Splunk roles could retrieve the Observability Cloud API access token through the Discover Splunk Observability Cloud app due to improper access control. This vulnerability does not affect Splunk Enterprise versions below 9.4.9 and 9.3.10 because the Discover Splunk Observability Cloud app does not come with Splunk Enterprise.

Impact

The primary impact of this vulnerability is unauthorized disclosure of the Observability Cloud API access token to low-privileged users. This token can be used to access observability data and services, which may include sensitive operational metrics, logs, and traces. Unauthorized access could enable attackers to gather intelligence about the target environment, manipulate monitoring data, or disrupt incident response efforts. While the vulnerability does not directly allow system compromise or availability disruption, the exposure of sensitive tokens can facilitate lateral movement or privilege escalation in complex environments. Organizations relying heavily on Splunk for observability and security monitoring could face increased risk of data leakage and reduced trust in their monitoring systems. The impact is particularly significant in environments where Splunk is integrated with critical infrastructure or where observability data is used for security analytics and compliance reporting.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

advisory.splunk.com/advisories/SVD-2026-0305 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 18 Mar 2026, 19:10 UTC

WeaknessesCWE-200

Technical details

References

Community reviews

Related threats