Loading vulnerability…
CVE-2026-20298 is a sensitive information disclosure vulnerability in Splunk Enterprise and Splunk Cloud Platform. In affected releases, the REST SPL command can return the encr_password result field when querying the stored-passwords REST resource. This permits authenticated low-privileged users that lack the admin and power roles to retrieve stored credential hashes.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A medium-severity information disclosure vulnerability in Splunk products that could allow attackers to view stored credential hashes.
A medium-severity information disclosure vulnerability in Splunk that allows a low-privileged authenticated user to access stored credential hashes via the storage/passwords REST endpoint through SPL.
A medium-severity information disclosure vulnerability in Splunk that allows a low-privileged user to view stored credential hashes via the storage/passwords endpoint using the |rest SPL command.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.