Server-Side Request Forgery (SSRF) through the Connectivity Check REST API in Splunk SOAR (CVE-2026-76361) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-76361

Server-Side Request Forgery (SSRF) through the Connectivity Check REST API in Splunk SOAR

Answer in brief

CVE-2026-76361 records a Unknown severity vulnerability in Server-Side Request Forgery (SSRF) through the Connectivity Check REST API in Splunk SOAR. The current sources do not mark it as known exploited. The current feed maps Splunk/Splunk SOAR (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 19, 2026Updated Aug 19, 2026Source checked Aug 19, 2026First seen by HOL Aug 19, 2026Material review Aug 19, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Splunk/Splunk SOAR (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Splunk/Splunk SOARgeneric	>=8.6 <8.6.0	8.6.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for Splunk/Splunk SOAR.
Review the reported fix. Update Splunk/Splunk SOAR to 8.6.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 19, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 19, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 19, 2026

Sources and claim methodology

Source referenceadvisory.splunk.com

Upstream source description

In Splunk SOAR versions below 8.6.0, a user with the "Administrator" role could use the /rest/support/connectivity/.../check_connectivity endpoint to make Splunk SOAR initiate outbound network connections to arbitrary destinations and determine whether internal hosts and ports are reachable. The Server-Side Request Forgery (SSRF) is possible because the connectivity check REST API does not sufficiently validate the destination before Splunk SOAR connects to it. For more information see Manage roles and permissions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.5.0/manage-your-splunk-soar-on-premises-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-on-premises) in the Splunk documentation.

Quoted source text, attributed separately from HOL analysis.