CVE Watchtower

CVE-2026-76272Splunk Splunk Missing Authorization

NVDCVSS scored by psirt@cisco.com

Vulnerability Summary

In Splunk Enterprise versions below 10.4.3, 10.2.7, 10.0.10, and 9.4.15, a user who does not hold the "admin" or "power" Splunk roles could cause Splunk Secure Gateway to sign attacker-controlled payloads. The vulnerability is possible because Splunk Secure Gateway does not verify that the user is authorized to request a signature. Splunk Secure Gateway versions below 3.10.11, 3.9.25, and 3.8.72 are also affected. For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.2/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) in the Splunk documentation.
Severity Level
MEDIUM(4.3)
Published Date
Oct 7, 2026
Last Modified
Oct 14, 2026
Exploitation Status
No confirmed exploitation yet
EPSS Score (30-Day)
0.22%Probability
Root Weakness (CWE)
The software does not perform an authorization check when an actor attempts to access a resource or perform an action.
CVSS v3.1 Base Metrics — Score 4.3 (MEDIUM)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityNone
IntegrityLow
AvailabilityNone

Affected & Patched Versions

Affected Versions
  • Splunk Splunk >= 9.4.0 and < 9.4.15
  • Splunk Splunk >= 10.0.0 and < 10.0.10
  • Splunk Splunk >= 10.2.0 and < 10.2.7
  • Splunk Splunk >= 10.4.0 and < 10.4.3
  • Splunk Splunk Secure Gateway >= 3.8.0 and < 3.8.72
  • Splunk Splunk Secure Gateway >= 3.9.0 and < 3.9.25
  • Splunk Splunk Secure Gateway >= 3.10.0 and < 3.10.11
Patched Versions
  • Splunk Splunk 9.4.15
  • Splunk Splunk 10.0.10
  • Splunk Splunk 10.2.7
  • Splunk Splunk 10.4.3
  • Splunk Splunk Secure Gateway 3.8.72
  • Splunk Splunk Secure Gateway 3.9.25
  • Splunk Splunk Secure Gateway 3.10.11

What to do

Fix it during your normal patch cycle. No exploitation is confirmed yet.

  1. Check whether you run Splunk Splunk and which version.
  2. Update to a patched version listed above, then confirm the new version.

Timeline

  • Oct 7, 2026Published
  • Oct 14, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new Splunk Splunk CVEsYou are reading CVE-2026-76272. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

Data last checked: Nov 17, 2026 19:13 UTC