Skip to content
VulniPulse
Low2.7Splunk

Low [CVE-2026-76361] Server-Side Request Forgery (SSRF) through the Connectivity Check REST API in Splunk SOAR

This low-severity Splunk advisory covers CVE-2026-76361 affecting Splunk SOAR.

CVE-2026-76361 Published Aug 19, 2026Updated by vendor Aug 19, 2026
Affected products & platforms
SplunkES / ITSI / SOAR
Open vendor advisory

Android app · Google Play

Monitor future Splunk CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

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) ( ) in the Splunk documentation.

Affected versions
  • Splunk SOAR 8.6 before 8.6.0

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Fixed versions
  • 8.6.0

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Mitigation

Upgrade to a fixed release: 8.6.0. That is the remediation for this advisory.

The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.