---
id: "CVE-2026-76308"
kind: "vulnerability"
aliases: ["CVE-2026-76308"]
title: "Splunk SOAR: any logged-in user can change the Enterprise Security license edition"
severity: "medium"
cvss: 6.5
epss: 0.00174
exploited: false
status: "open"
category: "other"
products: []
ecosystems: []
tags: ["on-premises", "other", "splunk-enterprise-security", "splunk-soar"]
not_affected_if: ["soar-8.7.0-or-later"]
published_at: "2026-10-21T23:17:29+00:00"
first_seen_at: "2026-10-23T21:57:29+00:00"
updated_at: "2026-10-25T03:48:46+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-76308", "first_seen_at": "2026-10-23T21:57:29+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-76308", "first_seen_at": "2026-10-24T13:15:54+00:00"}]
---

# Splunk SOAR: any logged-in user can change the Enterprise Security license edition

Splunk SOAR before 8.7.0 authenticates REST API requests to manage the Enterprise Security edition but does not check that the caller is authorized. An authenticated user can therefore switch the Enterprise Security edition and have SOAR apply the license change.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed SOAR version on the appliance or in the admin UI; versions below `8.7.0` are affected according to the sources
- Review which accounts hold valid SOAR credentials, since an authenticated user is required
- unknown whether a specific configuration changes exposure

## Fix

- Upgrade Splunk SOAR (On-premises) to `8.7.0` or later, as stated in the sources
- unknown whether a workaround or setting change exists before upgrading

## Timeline

- 2026-10-23T21:57:29+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-76308
- 2026-10-24T13:15:54+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-76308

## From the sources

In Splunk SOAR versions below 8.7.0, an authenticated user could change the Enterprise Security edition through the Representational State Transfer (REST) API and cause Splunk SOAR to apply the license change.
The vulnerability is possible because Splunk SOAR authenticates requests to manage the Enterprise Security edition but does not authorize the caller before it applies the license change.
For more information see Using the REST API reference for Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/rest-api-reference/8.7.0/using-the-splunk-soar-rest-api/using-the-rest-api-reference-for-splunk-soar-on-premises), Obtain and configure a Splunk SOAR (On-premises) license (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.7.0/configure-your-companys-settings-in-splunk-soar-on-premises/obtain-and-configure-a-splunk-soar-on-premises-license), and Integration of Splunk SOAR with Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.7/automation-with-playbooks/integration-of-splunk-soar-with-splunk-enterprise-security) in the Splunk documentation.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_