dbcve.org
SplunkApplication

CVE-2026-20254

MEDIUM · 5.7 CVSS v3.1 Published 2026-06-10
Fix available
A fix is available. Upgrade to 9.3.13 / 9.3.2411.132 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
In Splunk Enterprise versions below 10.2.4, 10.0.7, 9.4.12, and 9.3.13, and Splunk Cloud Platform versions below 10.3.2512.13, 10.2.2510.15, 10.1.2507.23, and 9.3.2411.132, a low-privileged user that does not hold the 'admin' or 'power' Splunk roles could craft a malicious classic dashboard that exfiltrates sensitive data to an external server when a higher-privileged user views it, bypassing the external content restriction through a Cascading Style Sheets (CSS) injection.<br><br>The Trusted Domains security check does not fully validate inline style attribute values, which can allow for outbound requests to untrusted domains and credential exfiltration when a victim views a crafted dashboard.

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 confidence

This is a CSS injection vulnerability in Splunk Enterprise and Cloud Platform where the Trusted Domains security check insufficiently validates inline style attribute values. A low-privileged user can craft a malicious classic dashboard containing CSS-based data exfiltration that triggers when a higher-privileged user views it, bypassing external content restrictions and sending sensitive data/credentials to untrusted external domains.

MitigationUpgrade Splunk Enterprise to versions 10.2.4, 10.0.7, 9.4.12, or 9.3.13 and above, or upgrade Splunk Cloud Platform to versions 10.3.2512.13, 10.2.2510.15, 10.1.2507.23, or 9.3.2411.132 and above.

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
SplunkApplication
Affected:>= 9.3.0, < 9.3.13>= 9.4.0, < 9.4.12>= 10.0.0, < 10.0.7>= 10.2.0, < 10.2.4
Splunk Cloud PlatformApplication
Affected:>= 9.3.2411, < 9.3.2411.132>= 10.1.2507, < 10.1.2507.23>= 10.2.2510, < 10.2.2510.15>= 10.3.2512, < 10.3.2512.13

CVSS 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Splunk Enterprise version
    Navigate to Settings > About > About Splunk Enterprise in the web UI, or run 'splunk --version' from the CLI. Compare the installed version against the affected ranges: 9.3.0 to 9.3.12, 9.4.0 to 9.4.11, 10.0.0 to 10.0.6, or 10.2.0 to 10.2.3.
    Affected if The installed version falls within any of these ranges.
  2. Check Splunk Cloud Platform version
    Access the Splunk Cloud Platform version information from the Cloud Portal or use the 'splunk _internal' API endpoint /services/server/info to retrieve the version. Compare against the affected ranges: 9.3.2411 to 9.3.2411.131, 10.1.2507 to 10.1.2507.22, 10.2.2510 to 10.2.2510.14, or 10.3.2512 to 10.3.2512.12.
    Affected if The installed version falls within any of these ranges.
  3. Verify classic dashboard usage
    Check for Simple XML dashboard definitions in the Splunk deployment by examining the $SPLUNK_HOME/etc/system/local/, $SPLUNK_HOME/etc/apps/, and $SPLUNK_HOME/etc/sharing/ directories for .xml files containing <form> or <dashboard> tags with Simple XML. Alternatively, query the saved searches REST endpoint to identify dashboards using the classic Simple XML format.
    Affected if Classic Simple XML dashboards exist in the environment.
  4. Check user role permissions for dashboard creation
    Examine Splunk authorization configuration in $SPLUNK_HOME/etc/system/local/authorize.conf or via the UI at Settings > Users and Roles. Determine if users with low-privileged roles (such as user or power) have capabilities to create or edit saved searches or dashboards.
    Affected if Low-privileged users have permissions to create or modify dashboards.
  5. Inspect Trusted Domains configuration
    Review the web.conf file at $SPLUNK_HOME/etc/system/local/web.conf for the [general] section and trustedDomain settings, or check via the UI at Settings > Server settings > General settings > Trusted domains. Verify if external domains are configured as trusted.
    Affected if External domains are configured as trusted and the version is within the affected range.

The environment is affected if the Splunk version falls within any of the listed vulnerable ranges AND classic dashboards exist AND low-privileged users can create or modify dashboards.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 9.3.13 / 9.3.2411.132 / 9.4.12 or later
Fixed in 9.3.139.3.2411.1329.4.12
Interim mitigation

Upgrade Splunk Enterprise to versions 10.2.4, 10.0.7, 9.4.12, or 9.3.13 and above, or upgrade Splunk Cloud Platform to versions 10.3.2512.13, 10.2.2510.15, 10.1.2507.23, or 9.3.2411.132 and above.

Recommended fix High confidence

Splunk Enterprise: 9.3.13, 9.4.12, 10.0.7, or 10.2.4 | Splunk Cloud Platform: 9.3.2411.132, 10.1.2507.23, 10.2.2510.15, or 10.3.2512.13

  1. Identify the currently installed Splunk Enterprise or Splunk Cloud Platform version using the 'About' page or 'splunk version' command
  2. For Splunk Enterprise: If running 9.3.x, upgrade to 9.3.13 or later; if running 9.4.x, upgrade to 9.4.12 or later; if running 10.0.x, upgrade to 10.0.7 or later; if running 10.2.x, upgrade to 10.2.4 or later
  3. For Splunk Cloud Platform: Contact Splunk Cloud support to request upgrade to the fixed version for your respective release branch (9.3.2411.132, 10.1.2507.23, 10.2.2510.15, or 10.3.2512.13)
  4. After upgrading, verify the fix by reviewing the Splunk Enterprise or Splunk Cloud Platform release notes for CVE-2026-20254
  5. Test that the Trusted Domains security check properly validates inline style attribute values in classic dashboards
Caveat Standard Splunk upgrade procedures apply; review Splunk Upgrade Guidelines for pre-upgrade checks and compatibility considerations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Splunk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-20254 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-20254 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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