CVE-2026-76407 — Improper Access Control in Splunk SOAR
As part of Cisco's ongoing commitment to proactive security and product quality, Cisco has conducted a comprehensive internal security review. This review resulted in a software hardening release that addresses multiple internally discovered vulnerabilities. The vulnerabilities tracked by CVE-2026-76407 are related to improper access control and are grouped under the Common Weakness Enumeration (CWE) CWE-284.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.1% (30-day exploitation probability)+0
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Splunk Splunk SOAR).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Splunk | Splunk SOAR | < 8.7.0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 22, 2026 → Oct 30, 2026 · 9 reading(s) · max 0.13%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Audit administrative actions and access to resources outside each user’s normal pattern.
Timeline
What happened to this CVE, newest first.
- 2026
- Source status changed · Received → Awaiting Analysis
- Record published
- Affected products added · splunk/splunk soar
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 21, 2026 – Oct 22, 2026
- 1× Official description updated · Oct 21, 2026 – Oct 21, 2026
References
3 on the record
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-76531 Files or Directories Accessible to External Parties in Splunk SOAR 10d
- High CVE-2026-76530 Use of Non-Canonical URL Paths for Authorization Decisions in Splunk SOAR 10d
- Critical CVE-2026-76408 Improper Control of a Resource Through its Lifetime in Splunk SOAR 10d
- High CVE-2026-76526 Improper Neutralization in Splunk SOAR 10d
- Medium CVE-2026-76406 Information Disclosure through REST API Authentication in Splunk SOAR 10d
- Medium CVE-2026-76308 Missing Authorization through the REST API in Splunk SOAR 10d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-76407 is "Improper Access Control in Splunk SOAR", rated Unknown. It affects Splunk SOAR (Splunk); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.13% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.