Repository metadata disclosure via missing permission check
Published Aug 19, 2026 · Updated Aug 20, 2026
Missing authorization in Splunk SOAR before 8.6.0 allows remote authenticated users to view unauthorized playbook repository metadata. Playbook History returns revision metadata without checking whether the caller is permitted to access the underlying repository. A role containing playbooks:view is required, and the consequence is limited to disclosure of repository metadata rather than playbook modification.
Summary
What happened
Missing authorization in Splunk SOAR before 8.6.0 allows remote authenticated users to view unauthorized playbook repository metadata. Playbook History returns revision metadata without checking whether the caller is permitted to access the underlying repository. A role containing playbooks:view is required, and the consequence is limited to disclosure of repository metadata rather than playbook modification.
The record
- CVE
- CVE-2026-76368
- Published
- Aug 19, 2026
- Updated
- Aug 20, 2026
- Vendor
- Splunk, Inc.
- Product
- Splunk SOAR
- Classifications
- CWE-862, T1213.003
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 19, 2026CVE publishedPublication date reported by the CVE source.
- Aug 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=8.6 <8.6.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo