In Splunk SOAR versions below 8.6.0, a user who holds the "Incident Commander" Splunk SOAR role could store JavaScript in a note and run it in the… (CVE-2026-76367)
Description
Splunk SOAR versions below 8.6.0 contain a stored Cross-Site Scripting (XSS) vulnerability that allows a user with the "Incident Commander" role to store JavaScript in a note. This script can execute in the browser of another user when they open the note. The vulnerability arises because note content is treated as HTML without proper sanitization when the note format changes. Exploitation requires tricking the victim into initiating a request in their browser. The vulnerability has a moderate severity score and no known exploits in the wild.
CVSS v3.1
Score 4.0medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In Splunk SOAR versions prior to 8.6.0, a stored XSS vulnerability (CVE-2026-76367) exists where users with the "Incident Commander" role can embed JavaScript in notes. When another user views the note, the script executes in their browser due to improper sanitization of note content treated as HTML during format changes. This vulnerability requires user interaction via phishing to trigger the malicious script. The CVSS 3.1 score is 4.0 (medium), reflecting network attack vector, high attack complexity, high privileges required, user interaction needed, and partial impact on confidentiality and integrity.
Potential Impact
An attacker with the "Incident Commander" role can inject malicious JavaScript into notes, which executes in the browsers of other users who view those notes. This can lead to partial confidentiality and integrity impacts within the Splunk SOAR environment. However, exploitation requires phishing to trick users into triggering the script, and the attacker cannot exploit the vulnerability arbitrarily. There are no known exploits in the wild.
Mitigation Recommendations
No official patch or fix information is provided in the available data. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict the "Incident Commander" role to trusted users only and educate users to be cautious of unexpected notes. Monitor vendor communications for updates regarding patches or official mitigations.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-w7fq-wgjx-63h9
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-76367"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a870a88acd9273b49b5a117
Added to database: 08/20/2026, 14:09:12 UTC
Last enriched: 08/20/2026, 14:44:55 UTC
Last updated: 10/05/2026, 06:48:18 UTC
Views: 33
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.