In Splunk SOAR versions below 8.6.0, an unauthenticated user could spoof the source IP address in a crafted request to an Automation Broker notification endpoint and execute arbitrary code on the Splunk SOAR host. The vulnerability is possible because the Splunk SOAR Automation Broker trusts a client-supplied source IP address header as proof that the request originates from the local system. Successful exploitation can expose all relevant data, affect system integrity, and disrupt service availability. For more information see About Splunk SOAR Automation Broker (https://help.splunk.com/en/splunk-soar/splunk-automation-broker/about-splunk-soar-automation-broker/about-splunk-soar-automation-broker) in the Splunk documentation.
CVE-2026-76356
Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-20. a secondary CVSS source baseline 8.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EG Score
- 8.1(high)
- EG Risk
- 37(Track)EG Risk 37/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity81% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 30%
- KEV
- Not listed
Published
August 19, 2026
Last Modified
August 21, 2026
Advisory Details (1)
Auto-updated Aug 19, 2026SVD-2026-0804 | Splunk Vulnerability Disclosure
https://advisory.splunk.com/advisories/SVD-2026-0804Vendor Advisories for CVE-2026-76356(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 13× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-21 04:35 UTCEG score recompute
- 2026-08-21 04:35 UTCGHSA enrichment
- 2026-08-21 04:00 UTCEG score recompute
- 2026-08-21 04:00 UTCGHSA enrichment
- 2026-08-21 00:30 UTCEG score recompute
- 2026-08-21 00:30 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 13:19 UTCGHSA enrichment
- 2026-08-20 09:31 UTCEG score recompute
- 2026-08-20 09:31 UTCGHSA enrichment
- 2026-08-19 22:21 UTCEG score recompute
- 2026-08-19 21:39 UTCEG score recompute
- 2026-08-19 21:37 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-76356?
When was CVE-2026-76356 disclosed?
Is CVE-2026-76356 actively exploited?
What is the CVSS score of CVE-2026-76356?
How do I remediate CVE-2026-76356?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-76356
Is Your Infrastructure Affected by CVE-2026-76356?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.