# CVE-2026-76367: Stored Cross-Site Scripting (XSS) through Notes in Splunk SOAR

> An Incident Commander can inject malicious JavaScript into notes, executing it in other users' browsers to potentially hijack sessions or execute code.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-w7fq-wgjx-63h9

## What is CVE-2026-76367?

CVE-2026-76367 is a medium-severity cross-site scripting vulnerability in Splunk SOAR, published on 19 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

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 browser of another user when that user opens the note. The stored Cross-Site Scripting (XSS) vulnerability is possible because Splunk SOAR can treat existing note content as Hypertext Markup Language (HTML) without sanitizing that content when the note format changes. The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The user who holds the "Incident Commander" Splunk SOAR role should not be able to exploit the vulnerability at will. For more information see Manage roles and permissions in Splunk SOAR (Cloud) (https://help.splunk.com/en/splunk-soar/soar-cloud/administer-soar-cloud/manage-your-splunk-soar-cloud-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-cloud) in the Splunk documentation.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-76367?

It affects 1 product.


Products: Splunk Soar.

## How do I fix CVE-2026-76367?

No fix has been published for CVE-2026-76367 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-76367 being exploited?

There is no known exploitation of CVE-2026-76367 in the wild and no public exploit code.

## Other vulnerabilities in Splunk SOAR

- [CVE-2023-3997](https://insights.sbomify.com/CVE-2023-3997/): Unauthenticated Log Injection In Splunk SOAR (high 8.6)
- [CVE-2026-76356](https://insights.sbomify.com/CVE-2026-76356/): Authentication Bypass through IP Address Spoofing in the Automation Broker in Splunk SOAR (high 8.1)
- [CVE-2026-76357](https://insights.sbomify.com/CVE-2026-76357/): Remote Code Execution (RCE) through Path Traversal in the REST API in Splunk SOAR (high 7.6)
- [CVE-2026-76362](https://insights.sbomify.com/CVE-2026-76362/): Improper Certificate Validation through CyberArk Vault Privileged Access Manager in Splunk SOAR (high 7.4)
- [CVE-2026-76358](https://insights.sbomify.com/CVE-2026-76358/): Path Traversal through App Installation Tar Extraction in Splunk SOAR (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-76367 and fix it if it is affected.

What it is: CVE-2026-76367 is a medium-severity cross-site scripting vulnerability in Splunk SOAR, published on 19 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-76367 in the wild and no public exploit code.

Affected product: Splunk SOAR. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-76367/ (Markdown: https://insights.sbomify.com/CVE-2026-76367/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-76367
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-76367
- OSV: https://osv.dev/vulnerability/CVE-2026-76367

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-76367/
Summaries are generated and may contain mistakes; the official description above is the record.