CVE-2026-20298
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.4.1, 10.2.5, 10.0.8, and 9.4.13, and Splunk Cloud Platform versions below 10.5.2605.0, 10.4.2604.6, 10.3.2512.15, 10.2.2510.18, and 10.1.2507.24, a low-privileged user that does not hold the 'admin' or 'power' Splunk roles could view stored credential hashes when they access the `/servicesNS/-/-/storage/passwords` REST endpoint through the `|rest` Search Processing Language (SPL) command.<br><br>The exposure happens because the `|rest` SPL command returns the `encr_password` field in the results of the `/servicesNS/-/-/storage/passwords` REST endpoint.
In the news
Third-party coverageSurfaced from public web coverage — external links open in a new tab.
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 confidenceA low-privileged Splunk user (non-admin/non-power roles) can access the `/servicesNS/-/-/storage/passwords` REST endpoint through the `|rest` SPL command and retrieve the `encr_password` field containing stored credential hashes that should be restricted from such users.
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>= 9.4.0, < 9.4.13>= 10.0.0, < 10.0.8>= 10.2.0, < 10.2.5= 10.4.0>= 10.1.2507, < 10.1.2507.24>= 10.2.2510, < 10.2.2510.18>= 10.3.2512, < 10.3.2512.15>= 10.4.2604, < 10.4.2604.6CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check Splunk Enterprise versionRun: splunk --version or access About > Version in Splunk Web. Compare the installed version to affected ranges: 9.4.0 to 9.4.12, 10.0.0 to 10.0.7, 10.2.0 to 10.2.4, or exactly 10.4.0Affected if The installed version falls within any of the affected ranges listed in the CVE (9.4.x before 9.4.13, 10.0.x before 10.0.8, 10.2.x before 10.2.5, or exactly 10.4.0)
-
Verify low-privilege user can execute |rest commandAs a non-admin/non-power user, run: | rest /servicesNS/-/-/storage/passwordsAffected if The command executes without permission errors and returns output containing credential data
-
Check for exposed encr_password fieldExecute as a low-privilege user: | rest /servicesNS/-/-/storage/passwords | table name encr_passwordAffected if The output contains non-empty values in the encr_password column for any stored credentials
-
Inspect user role permissionsNavigate to Settings > Users and Roles or run: | rest /services/admin/roles | table roleName srchEventsAllowed srchIndexesAllowedAffected if Users with user or power roles (not admin) can access the storage/passwords endpoint through the |rest command
You are affected if your Splunk version is within the vulnerable ranges AND low-privileged users can access the /servicesNS/-/-/storage/passwords endpoint and retrieve encr_password field values.
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.4.1310.0.810.1.2507.24
Upgrade Splunk Enterprise to versions 10.4.1, 10.2.5, 10.0.8, or 9.4.13 (or later), and Splunk Cloud Platform to the fixed versions listed. Alternatively, restrict or audit access to the storage/passwords endpoint for non-privileged users.
Splunk Enterprise: 9.4.13, 10.0.8, 10.2.5, or 10.4.1+ | Splunk Cloud Platform: 10.1.2507.24, 10.2.2510.18, 10.3.2512.15, 10.4.2604.6, or 10.5.2605.0+
- 1. Identify the current Splunk Enterprise or Splunk Cloud Platform version using the About page in Splunk Web or the 'splunk version' CLI command.
- 2. For Splunk Enterprise: Upgrade to version 9.4.13, 10.0.8, 10.2.5, or 10.4.1 (or later) depending on your current major version branch.
- 3. For Splunk Cloud Platform: Contact Splunk Support to schedule an upgrade to version 10.1.2507.24, 10.2.2510.18, 10.3.2512.15, 10.4.2604.6, or 10.5.2605.0 (or later) depending on your current version.
- 4. After upgrade, verify that low-privileged users can no longer access the 'encr_password' field via the |rest command accessing /servicesNS/-/-/storage/passwords.
- 5. Review user roles and permissions to ensure the principle of least privilege is applied to credentials storage.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-20298 — 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-20298 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