Information Disclosure in Splunk Enterprise (CVE-2026-20298)
Summary
Vulnerability in Splunk Enterprise (CVE-2026-20298). Confidential information can be exposed externally. Exploitable via encr_password.
Original description
The description as published by the source.
In 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.The exposure happens because the |rest SPL command returns the encr_password field in the results of the /servicesNS/-/-/storage/passwords REST endpoint.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-20298 has been found in Splunk Enterprise.
Attackers can target a specific entry point like encr_password over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Splunk Enterprise CVE-2026-20298" on the vendor's site.
CVE-2026-20298 (Splunk Enterprise) — CWE-200 / CVSS v3 5.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: encr_password
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Information disclosure (CWE-200) exists in Splunk Enterprise. Attackers reach the vulnerable code path via encr_password.
Check the vendor advisory for the affected versions of Splunk Enterprise. Attack surface: encr_password.
Severity: Medium (CVSS 5.3/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Splunk Enterprise を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- patch psirt@cisco.com
- web nvd.nist.gov
- web github.com