CVE-2026-20259
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is an authorization bypass vulnerability in Splunk Enterprise and Cloud Platform where the saved search ownership reassignment endpoint lacks proper access control checks. Users with the high-privilege 'edit_saved_search_owner' capability can reassign saved search ownership to users outside their authorized scope, enabling privilege escalation beyond the intended role permissions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 10.0.0, < 10.0.7>= 10.2.0, < 10.2.4>= 9.3.2411, < 9.3.2411.131>= 10.0.2503, < 10.0.2503.14>= 10.1.2507, < 10.1.2507.23>= 10.2.2510, < 10.2.2510.15>= 10.3.2512, < 10.3.2512.12CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Splunk Enterprise versionRun 'splunk --version' from the Splunk bin directory, or view the version in the web UI under Settings > About > VersionAffected if The version is >= 10.0.0 and < 10.0.7, or >= 10.2.0 and < 10.2.4
-
Check Splunk Cloud Platform versionAccess the Cloud Platform health dashboard or version information in the administration interfaceAffected if The version is one of the affected Cloud Platform ranges listed in the CVE (9.3.2411 through 9.3.2411.131, 10.0.2503 through 10.0.2503.14, 10.1.2507 through 10.1.2507.23, 10.2.2510 through 10.2.2510.15, or 10.3.2512 through 10.3.2512.12)
-
Identify roles with edit_saved_search_owner capabilityNavigate to Settings > Users, Authentication, and Access Control > Roles in the Splunk web interface, or inspect the $SPLUNK_HOME/etc/system/local/authorize.conf fileAffected if Any role has the 'edit_saved_search_owner' capability enabled and is assigned to users who should not have broad ownership reassignment privileges
-
Audit users assigned the edit_saved_search_owner capabilityReview the user list under Settings > Users and Authentication > Users to see which users hold roles containing the 'edit_saved_search_owner' capabilityAffected if Users outside the intended administrative scope possess this capability, creating potential for unauthorized ownership reassignment
Your environment is affected if you are running a Splunk version within the affected ranges AND any user has been granted the 'edit_saved_search_owner' capability beyond your intended access boundaries.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped9.3.2411.13110.0.710.0.2503.14
Upgrade Splunk Enterprise to version 10.2.4, 10.0.7, or later; or upgrade Splunk Cloud Platform to the patched versions (10.4.2604.0, 10.3.2512.12, 10.2.2510.15, 10.1.2507.23, 10.0.2503.14, or 9.3.2411.131). Alternatively, review and restrict the 'edit_saved_search_owner' capability to only those users who absolutely require it.
Splunk Enterprise: 10.0.7 or 10.2.4+ | Splunk Cloud Platform: 9.3.2411.131, 10.0.2503.14, 10.1.2507.23, 10.2.2510.15 or later (contact Splunk for latest Cloud versions)
- Review current Splunk deployment and confirm installed version matches the affected versions
- Review Splunk upgrade documentation for your deployment type (Splunk Enterprise or Splunk Cloud Platform)
- Create a backup of your Splunk configuration and data
- Test the upgrade in a non-production environment first
- For Splunk Enterprise: Upgrade to version 10.0.7 or 10.2.4 or later
- For Splunk Cloud Platform: Upgrade to version 9.3.2411.131, 10.0.2503.14, 10.1.2507.23, 10.2.2510.15, or later (check with Splunk support for latest available)
- Verify the upgrade was successful
- Review that the edit_saved_search_owner capability is only assigned to roles that require it
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-20259 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-20259 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data