CVE-2026-20259 | Improper Access Control in Splunk Enterprise

In Splunk Enterprise versions below 10.2.4 and 10.0.7, and Splunk Cloud Platform versions below 10.4.2604.0, 10.3.2512.12, 10.2.2510.15, 10.1.2507.23, 10.0.2503.14, and 9.3.2411.131, a user who holds a Splunk role that contains the high-privilege capability `edit_saved_search_owner` could reassign saved search ownership to users outside their authorized scope. The ownership reassignment endpoint lacks access control.

Published: 2026-06-10 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-20259 is rated Low Risk (25.2/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.19%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-20259

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.03% 0.19% +0.16%
2 2026-06-11 — 0.03% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-20259

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 1.2 4.2 [email protected]

Weakness enumeration for CVE-2026-20259

GitHub Security Advisory for CVE-2026-20259

GHSA-jhf8-vwfv-vr95 · Severity: medium — In Splunk Enterprise versions below 10.2.4 and 10.0.7, and Splunk Cloud Platform versions below...

Affected software / configurations for CVE-2026-20259

Vendor Product Version Raw CPE
splunk splunk >= 10.0.0, < 10.0.7 cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*
splunk splunk >= 10.2.0, < 10.2.4 cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*
splunk splunk_cloud_platform >= 9.3.2411, < 9.3.2411.131 cpe:2.3:a:splunk:splunk_cloud_platform:*:*:*:*:*:*:*:*
splunk splunk_cloud_platform >= 10.0.2503, < 10.0.2503.14 cpe:2.3:a:splunk:splunk_cloud_platform:*:*:*:*:*:*:*:*
splunk splunk_cloud_platform >= 10.1.2507, < 10.1.2507.23 cpe:2.3:a:splunk:splunk_cloud_platform:*:*:*:*:*:*:*:*
splunk splunk_cloud_platform >= 10.2.2510, < 10.2.2510.15 cpe:2.3:a:splunk:splunk_cloud_platform:*:*:*:*:*:*:*:*
splunk splunk_cloud_platform >= 10.3.2512, < 10.3.2512.12 cpe:2.3:a:splunk:splunk_cloud_platform:*:*:*:*:*:*:*:*

References for CVE-2026-20259

cvelogic Threat Intelligence