Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-76356 – Authentication Bypass / Remote Code Execution – Splunk SOAR below 8.6.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-76356 is a high-severity authentication bypass vulnerability affecting the Automation Broker component of Splunk SOAR. An unauthenticated attacker can spoof a client-supplied source IP address header to trick the Automation Broker notification endpoint into treating the request as originating from the local, trusted system, ultimately enabling arbitrary code execution. The flaw affects all Splunk SOAR versions below 8.6.0 and carries a CVSS v3.1 base score of 8.1 (High).

Technical details

  • Root cause: The Automation Broker notification endpoint relies on a client-supplied source IP address header as evidence that a request originates from the local system, rather than validating the true network origin of the request (CWE-290: Improper Authentication).
  • Trigger conditions: An attacker sends a crafted request to the Automation Broker notification endpoint with a spoofed source IP header designed to make the request appear as if it came from localhost/the trusted host.
  • Attack vector: Network — the vulnerability can be exploited remotely without authentication (AV:N, PR:N, UI:N) and does not require any prior access or user interaction, though attack complexity is rated high (AC:H).
  • Impact: Successful exploitation allows an unauthenticated attacker to execute arbitrary code on the affected Splunk SOAR instance, with full impact to confidentiality, integrity, and availability (C:H/I:H/A:H) — potentially exposing sensitive data, tampering with automation playbooks/configurations, and disrupting SOAR operations.

Affected software

  • Splunk SOAR: all versions below 8.6.0

Severity

  • CVSS v3.1 Base Score: 8.1 (High)
  • Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade Splunk SOAR to version 8.6.0 or higher, which enforces proper origin validation for the Automation Broker notification endpoint instead of trusting client-supplied IP headers.
  • If immediate patching is not possible: Restrict and firewall network access to the Splunk SOAR Automation Broker endpoint so that it is reachable only from trusted internal hosts, and monitor for anomalous requests to the notification endpoint that attempt to spoof local-origin headers. These measures reduce exposure but do not eliminate the underlying flaw — upgrading remains the only complete fix.
  • Note: This advisory also addresses several related, separately tracked vulnerabilities in the same Splunk SOAR release (e.g., a REST API path traversal RCE and a CyberArk integration certificate-validation issue); organizations upgrading to 8.6.0 should review the full vendor advisory to confirm all applicable post-upgrade configuration steps.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge