{ "dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": { "cveId": "CVE-2026-76273", "assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633", "state": "PUBLISHED", "assignerShortName": "cisco", "dateReserved": "2026-08-19T12:02:03.620Z", "datePublished": "2026-10-07T20:46:33.936Z", "dateUpdated": "2026-10-07T20:46:33.936Z" }, "containers": { "cna": { "affected": [ { "product": "Splunk Enterprise", "vendor": "Splunk", "versions": [ { "version": "10.4", "status": "affected", "versionType": "custom", "lessThan": "10.4.3" }, { "version": "10.2", "status": "affected", "versionType": "custom", "lessThan": "10.2.7" }, { "version": "10.0", "status": "affected", "versionType": "custom", "lessThan": "10.0.10" }, { "version": "9.4", "status": "affected", "versionType": "custom", "lessThan": "9.4.15" } ], "modules": [ "splunkd" ] } ], "descriptions": [ { "lang": "en", "supportingMedia": [ { "base64": false, "type": "text/markdown", "value": "In Splunk Enterprise versions below 10.4.3, 10.2.7, 10.0.10, and 9.4.15, a user that holds a role with the `run_collect` capability could use the `collect` Search Processing Language (SPL) command to add attacker-controlled content to system-level messages on the Splunk platform instance. The vulnerability is possible because the `collect` command does not validate the index name before processing the value. For more information see [collect](https://help.splunk.com/en/splunk-enterprise/search/spl-search-reference/10.4/search-commands/collect), [Define roles on the Splunk platform with capabilities](https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities), and [System endpoint descriptions](https://help.splunk.com/en/splunk-enterprise/rest-api-reference/10.4/system-endpoints/system-endpoint-descriptions) in the Splunk documentation." } ], "value": "In Splunk Enterprise versions below 10.4.3, 10.2.7, 10.0.10, and 9.4.15, a user that holds a role with the run_collect capability could use the collect Search Processing Language (SPL) command to add attacker-controlled content to system-level messages on the Splunk platform instance. The vulnerability is possible because the collect command does not validate the index name before processing the value. For more information see collect (https://help.splunk.com/en/splunk-enterprise/search/spl-search-reference/10.4/search-commands/collect), Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities), and System endpoint descriptions (https://help.splunk.com/en/splunk-enterprise/rest-api-reference/10.4/system-endpoints/system-endpoint-descriptions) in the Splunk documentation." } ], "references": [ { "url": "https://advisory.splunk.com/advisories/SVD-2026-1001" } ], "title": "Improper Input Validation through the collect Command in Splunk Enterprise", "datePublic": "2026-10-07T00:00:00.000Z", "problemTypes": [ { "descriptions": [ { "lang": "en", "type": "cwe", "cweId": "CWE-20", "description": "The product does not validate or incorrectly validates input that can affect the control flow or data flow of a program." } ] } ], "source": { "advisory": "SVD-2026-1001", "discovery": "" }, "providerMetadata": { "orgId": "d1c1063e-7a18-46af-9102-31f8928bc633", "shortName": "cisco", "dateUpdated": "2026-10-07T20:46:33.936Z" }, "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" } ] } ], "solutions": [ { "lang": "en", "value": "Upgrade Splunk Enterprise to versions 10.4.3, 10.2.7, 10.0.10, and 9.4.15, or higher." } ], "credits": [ { "lang": "en", "value": "Anton (therceman)", "type": "reporter" } ] } } }