CVE-2026-20166
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.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.
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 confidenceThe Discover Splunk Observability Cloud app in Splunk Enterprise and Cloud Platform versions lacks proper access control, allowing low-privileged users (non-admin/non-power roles) to retrieve sensitive Observability Cloud API access tokens through the app's interface.
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.4= 10.2.0>= 10.0.2503, < 10.0.2503.12>= 10.1.2507, < 10.1.2507.16>= 10.2.2510, < 10.2.2510.5CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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 command line, or in Splunk UI go to Settings > About > Version, or inspect the file $SPLUNK_HOME/etc/splunk.versionAffected if Version is 10.0.0 through 10.0.3, or exactly 10.2.0 (these are within the affected ranges)
-
Check Splunk Cloud Platform versionIn Splunk Cloud, view the version from the Cloud Portal or contact Splunk Cloud administrator for the version numberAffected if Version is 10.0.2503 through 10.0.2503.11, 10.1.2507 through 10.1.2507.15, or 10.2.2510 through 10.2.2510.4 (these are within the affected ranges)
-
Verify if Discover Splunk Observability Cloud app is installedCheck for the app directory at $SPLUNK_HOME/etc/apps/SA-O11y or search for 'Observability' in the Apps menu (Settings > Apps > Apps browser)Affected if The Discover Splunk Observability Cloud app or SA-O11y app is installed and enabled
-
Identify user roles with access to the Observability appIn Splunk UI, go to Settings > Users and Authentication > Users to view role assignments, then cross-reference with users who have access to the Observability appAffected if Any user with a role other than admin or power (such as user or custom limited roles) has access to the Observability app interface
-
Check for exposed API tokens in app configurationInspect the local configuration for the Observability app in $SPLUNK_HOME/etc/apps/SA-O11y/local/ for any stored API tokens or credentials, or check via CLI: splunk cmd python -m simplejson $SPLUNK_HOME/etc/apps/SA-O11y/local/inputs.confAffected if Sensitive Observability Cloud API access tokens are visible or accessible in the app configuration that low-privileged users can retrieve through the app interface
A user is affected if they run a vulnerable Splunk version (Enterprise 10.0.0-10.0.3 or 10.2.0, or Cloud Platform within the listed ranges) AND have the Discover Splunk Observability Cloud app installed with non-admin users able to access it.
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 · scoped10.0.410.0.2503.1210.1.2507.16
Upgrade Splunk Enterprise to version 10.2.1/10.0.4 or later, or Splunk Cloud Platform to 10.2.2510.5/10.1.2507.16/10.0.2503.12 or later to patch the improper access control in the Discover Splunk Observability Cloud app.
Splunk Enterprise: 10.0.4 or 10.2.1+ | Splunk Cloud Platform: 10.0.2503.12+, 10.1.2507.16+, or 10.2.2510.5+
- Identify your current Splunk Enterprise or Splunk Cloud Platform version
- For Splunk Enterprise: Upgrade to version 10.0.4 or higher, or 10.2.1 or higher
- For Splunk Cloud Platform: Upgrade to version 10.0.2503.12 or higher, 10.1.2507.16 or higher, or 10.2.2510.5 or higher
- After upgrading, verify that the Discover Splunk Observability Cloud app no longer exposes API tokens to low-privileged users
- Confirm the upgrade by checking Splunk Cloud Platform release notes or the advisory at advisory.splunk.com
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-20166 — 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-20166 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