{"id":"CVE-2026-76272","state":"PUBLISHED","title":"Missing Access Control through the REST API in Splunk Secure Gateway","description":"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.","publishedAt":"2026-10-07T20:46:33.402Z","updatedAt":"2026-10-08T15:07:56.769Z","severity":{"score":4.3,"label":"Medium","version":"3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","source":"cisco"},"assigner":"cisco","products":["Splunk Splunk Enterprise","Splunk Splunk Secure Gateway"],"affected":[{"vendor":"Splunk","product":"Splunk Enterprise","versions":[{"version":"10.4","status":"affected","lessThan":"10.4.3","versionType":"custom"},{"version":"10.2","status":"affected","lessThan":"10.2.7","versionType":"custom"},{"version":"10.0","status":"affected","lessThan":"10.0.10","versionType":"custom"},{"version":"9.4","status":"affected","lessThan":"9.4.15","versionType":"custom"}],"modules":["REST API"]},{"vendor":"Splunk","product":"Splunk Secure Gateway","versions":[{"version":"3.10","status":"affected","lessThan":"3.10.11","versionType":"custom"},{"version":"3.9","status":"affected","lessThan":"3.9.25","versionType":"custom"},{"version":"3.8","status":"affected","lessThan":"3.8.72","versionType":"custom"}]}],"references":["https://advisory.splunk.com/advisories/SVD-2026-1001"],"weaknesses":["CWE-862"],"ingestedAt":"2026-10-29T20:12:58.252Z","source":{"repository":"CVEProject/cvelistV5","path":"cves/2026/76xxx/CVE-2026-76272.json","commit":"556c9d3a8cd17e218bb8e452ba7cd619a384ff47"},"raw":{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-76272","state":"PUBLISHED","datePublished":"2026-10-07T20:46:33.402Z","dateUpdated":"2026-10-08T15:07:56.769Z","assignerShortName":"cisco","assignerOrgId":"d1c1063e-7a18-46af-9102-31f8928bc633","dateReserved":"2026-08-19T12:02:03.620Z"},"containers":{"cna":{"title":"Missing Access Control through the REST API in Splunk Secure Gateway","descriptions":[{"lang":"en","value":"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."}],"affected":[{"vendor":"Splunk","product":"Splunk Enterprise","versions":[{"version":"10.4","status":"affected","lessThan":"10.4.3","versionType":"custom"},{"version":"10.2","status":"affected","lessThan":"10.2.7","versionType":"custom"},{"version":"10.0","status":"affected","lessThan":"10.0.10","versionType":"custom"},{"version":"9.4","status":"affected","lessThan":"9.4.15","versionType":"custom"}],"modules":["REST API"]},{"vendor":"Splunk","product":"Splunk Secure Gateway","versions":[{"version":"3.10","status":"affected","lessThan":"3.10.11","versionType":"custom"},{"version":"3.9","status":"affected","lessThan":"3.9.25","versionType":"custom"},{"version":"3.8","status":"affected","lessThan":"3.8.72","versionType":"custom"}]}],"references":[{"url":"https://advisory.splunk.com/advisories/SVD-2026-1001"}],"metrics":[{"cvssV3_1":{"vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1","baseScore":4.3,"baseSeverity":"MEDIUM"},"format":"CVSS","scenarios":[{"lang":"en","value":"GENERAL"}]}],"problemTypes":[{"descriptions":[{"cweId":"CWE-862","lang":"en","type":"cwe","description":"The software does not perform an authorization check when an actor attempts to access a resource or perform an action."}]}],"providerMetadata":{"shortName":"cisco","orgId":"d1c1063e-7a18-46af-9102-31f8928bc633","dateUpdated":"2026-10-07T20:46:33.402Z"},"datePublic":"2026-10-07T00:00:00.000Z","source":{"advisory":"SVD-2026-1001","discovery":"INTERNAL"},"solutions":[{"lang":"en","value":"Upgrade Splunk Enterprise to versions 10.4.3, 10.2.7, 10.0.10, and 9.4.15, or higher.\n\nUpgrade Splunk Secure Gateway to versions 3.10.11, 3.9.25, and 3.8.72, or higher."}],"workarounds":[{"lang":"en","value":"Turn off or remove the Splunk Secure Gateway app. See [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation. Note: Splunk Mobile, Spacebridge, and Mission Control rely on functionality in the Splunk Secure Gateway app. If you do not use any of these apps, features, or functionality, as a potential mitigation, you may turn off or remove the app."}],"credits":[{"lang":"en","value":"Gabriel Nitu, Splunk","type":"finder"}]},"adp":[{"title":"CISA ADP Vulnrichment","metrics":[{"other":{"type":"ssvc","content":{"timestamp":"2026-10-08T15:07:40.538192Z","id":"CVE-2026-76272","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}}}],"providerMetadata":{"shortName":"CISA-ADP","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","dateUpdated":"2026-10-08T15:07:56.769Z"}}]}}}