Cross-tenant identifier disclosure via missing REST authorization
Published Aug 19, 2026 · Updated Aug 20, 2026
Incorrect authorization in Splunk SOAR before 8.6.0 allows remote authenticated users to view out-of-scope tenant names and identifiers. With multi-tenancy enabled, the REST API returns tenant information without enforcing the requesting user's role-based tenant restrictions. Access requires a valid account assigned restricted tenant access; exposure is limited to names and identifiers of other tenants, with no reported data modification or service interruption.
Summary
What happened
Incorrect authorization in Splunk SOAR before 8.6.0 allows remote authenticated users to view out-of-scope tenant names and identifiers. With multi-tenancy enabled, the REST API returns tenant information without enforcing the requesting user's role-based tenant restrictions. Access requires a valid account assigned restricted tenant access; exposure is limited to names and identifiers of other tenants, with no reported data modification or service interruption.
The record
- CVE
- CVE-2026-76370
- Published
- Aug 19, 2026
- Updated
- Aug 20, 2026
- Vendor
- Splunk, Inc.
- Product
- Splunk SOAR
- Classifications
- CWE-863
- 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