Skip to main content

Splunk SOAR EUVDEUVD-2026-62926

| CVE-2026-76361 LOW
Server-Side Request Forgery (SSRF) (CWE-918)
2026-08-19 cisco GHSA-fjjw-8v57-f2fq
2.7
CVSS 3.1 · Vendor: cisco
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain SOAR Administrator credentials
  2. Delivery
    Authenticate to SOAR REST API
  3. Exploit
    Submit crafted connectivity check requests with internal destinations
  4. Execution
    SOAR initiates outbound probes to arbitrary hosts/ports
  5. Impact
    Analyze responses to map reachable internal network topology

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Credential Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires a valid account with the 'Administrator' role in Splunk SOAR On-premises - this is not a default user role and must be explicitly assigned per Splunk's role-based access control model (documented at 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). No special non-default configuration is required beyond having network access to the SOAR REST API - the vulnerable endpoint exists in default deployments. Exploitation is bounded by the SOAR instance's own network reachability; impact is limited to internal network enumeration (host/port discovery) with no direct path to data exfiltration, code execution, or integrity modification. Scope does not change (S:U), so the attacker cannot pivot to compromise other systems solely through this vulnerability.

Impact

The NVD-assigned CVSS score of 2.7 (Low) is appropriate and consistent with the actual risk profile. The PR:H metric is the dominant risk limiter: exploitation requires control of an Administrator-level account, which already grants extensive access to Splunk SOAR itself. The C:L impact reflects that an attacker gains only network topology information (host reachability, port status), not credential material or application data. No EPSS score is available in the provided data, but given the high privilege requirement and low confidentiality impact, a low EPSS would be expected. The vulnerability is not listed in CISA KEV, and no public proof-of-concept exploit code has been identified. The primary realistic threat is an insider threat scenario or post-compromise lateral reconnaissance by an attacker who has already obtained SOAR admin credentials. In environments that enforce strict SOAR admin account controls and MFA, residual risk is minimal.

Exploit ScenarioDerived

An attacker who has obtained Splunk SOAR Administrator credentials - via phishing, credential stuffing, or lateral movement from a compromised SOC workstation - authenticates to the SOAR REST API and iterates through internal RFC-1918 address ranges and common port numbers using the /rest/support/connectivity/.../check_connectivity endpoint. The SOAR platform, which typically has broad internal network access to reach security tooling, acts as a proxy scanner, returning reachability status for each probe and mapping internal network segments otherwise unreachable from the attacker's position. No public exploit code is required given the simplicity of crafting the HTTP requests.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 19, 2026

Splunk SOAR versions below 8.6.0 contain a Server-Side Request Forgery flaw in the connectivity check REST API endpoint (/rest/support/connectivity/.../check_connectivity) that allows an authenticated Administrator-role user to direct the SOAR platform to initiate outbound network connections to arbitrary destinations. This enables internal network enumeration - discovering reachable hosts and open ports using the SOAR instance's network position, which is typically privileged within enterprise SOC environments. No public exploit code has been identified and the vulnerability is not listed in CISA KEV; the CVSS score of 2.7 (Low) accurately reflects the high privilege prerequisite, though the risk is elevated in environments where the SOAR platform has broad internal network access.

RemediationAI

Upgrade Splunk SOAR to version 8.6.0 or later, as confirmed by the Splunk vendor advisory SVD-2026-0804 (https://advisory.splunk.com/advisories/SVD-2026-0804). As a compensating control where immediate patching is not possible, restrict access to the /rest/support/connectivity/ API path via network-layer controls or web application firewall rules to prevent use of this endpoint from non-trusted management IP ranges - note this may interrupt legitimate administrative connectivity diagnostics. Additionally, auditing and tightening which accounts hold the Administrator role in Splunk SOAR reduces the attack surface; the fewer accounts with that role, the narrower the exploitation window. Enabling SOAR outbound firewall egress restrictions to known-good destinations would limit the utility of the SSRF for internal probing even if triggered.

Affected VersionsENISA

Splunk SOAR 8.6 <8.6.0

Affected Packages

euvd splunk_soar fix: 8.6.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Splunk SOAR (formerly Phantom) is an enterprise Security Orchestration, Automation and Response platform used in SOC environments to automate incident response workflows. The affected component is a REST API endpoint designed for legitimate administrative connectivity diagnostics. The root cause is CWE-918 (Server-Side Request Forgery): the application accepts user-supplied destination parameters for outbound connections without sufficiently validating or restricting permissible targets, allowing the server to act as a proxy to internal network resources. Per CPE cpe:2.3:a:splunk:splunk_soar, all Splunk SOAR versions in the 8.x line below 8.6.0 are affected. Because SOAR platforms are routinely deployed with wide internal network reachability to enable automation across diverse security tooling, this SSRF is particularly useful for network reconnaissance from a privileged vantage point.

Know when Splunk gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (cisco) PRIMARY 2.7 LOW
AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N
vuln.today AI 2.7 LOW

Administrator role is required (PR:H); impact is limited to internal network topology disclosure (C:L) with no integrity or availability effect.

3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (cisco).

CVSS VectorVendor: cisco

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Lifecycle Timeline

1
Patch available
Aug 19, 2026 - 22:04 EUVD

DescriptionCVE.org

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.

Threat Intelligence Overview

EPSS Score
0.2%
Top 87% exploitable
Prevalence
Medium
enterprise SOC platform, deployed in large security operations centers
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity LOW
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Low
Technical Impact
Partial

Priority Score

14
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +14
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.

More in Splunk

View all
CVE-2014-0160 HIGH POC
7.5 Apr 07

The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packe

CVE-2026-20253 CRITICAL POC
9.8 Jun 10

Unauthenticated arbitrary file write in Splunk Enterprise (below 10.2.4 and 10.0.7) and Splunk Cloud Platform (below 10.

CVE-2021-22901 HIGH POC
8.1 Jun 11

curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when

CVE-2022-32206 MEDIUM POC
6.5 Jul 07

curl < 7.84.0 supports "chained" HTTP compression algorithms, meaning that a serverresponse can be compressed multiple t

CVE-2024-36985 HIGH POC
8.8 Jul 01

In Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10, a low-privileged user that does not hold the admin or powe

CVE-2023-46214 HIGH POC
8.8 Nov 16

In Splunk Enterprise versions below 9.0.7 and 9.1.2, Splunk Enterprise does not safely sanitize extensible stylesheet la

CVE-2023-32707 HIGH POC
8.8 Jun 01

In versions of Splunk Enterprise below 9.0.5, 8.2.11, and 8.1.14, and Splunk Cloud Platform below version 9.0.2303.100,

CVE-2022-43571 HIGH POC
8.8 Nov 03

In Splunk Enterprise versions below 8.2.9, 8.1.12, and 9.0.2, an authenticated user can execute arbitrary code through t

CVE-2022-32207 CRITICAL POC
9.8 Jul 07

When curl < 7.84.0 saves cookies, alt-svc and hsts data to local files, it makes the operation atomic by finalizing the

CVE-2022-35737 HIGH POC
7.5 Aug 03

SQLite 1.0.12 through 3.39.x before 3.39.2 sometimes allows an array-bounds overflow if billions of bytes are used in a

CVE-2022-43551 HIGH POC
7.5 Dec 23

A vulnerability exists in curl <7.87.0 HSTS check that could be bypassed to trick it to keep using HTTP. Rated high seve

CVE-2022-32221 CRITICAL POC
9.8 Dec 05

When doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data t

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy