{
    "dataType": "CVE_RECORD",
    "dataVersion": "5.2",
    "cveMetadata": {
        "cveId": "CVE-2026-76270",
        "assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
        "state": "PUBLISHED",
        "assignerShortName": "cisco",
        "dateReserved": "2026-08-19T12:02:03.620Z",
        "datePublished": "2026-10-07T20:46:32.327Z",
        "dateUpdated": "2026-10-07T20:46:32.327Z"
    },
    "containers": {
        "cna": {
            "affected": [
                {
                    "product": "Splunk Enterprise",
                    "vendor": "Splunk",
                    "versions": [
                        {
                            "version": "10.4",
                            "status": "affected",
                            "versionType": "custom",
                            "lessThan": "10.4.3"
                        }
                    ],
                    "modules": [
                        "REST API"
                    ]
                }
            ],
            "descriptions": [
                {
                    "lang": "en",
                    "supportingMedia": [
                        {
                            "base64": false,
                            "type": "text/markdown",
                            "value": "In Splunk Enterprise versions below 10.4.3, a user that holds a role with the `list_spl2_modules` capability could use SQL injection in SPL2 module filtering to access all relevant data available through the affected Representational State Transfer (REST) API, including private SPL2 module definitions belonging to other users. The vulnerability is possible because Splunk Enterprise and Splunk Cloud Platform do not parameterize user-supplied values before using them in database queries for SPL2 module filtering. For more information see [Manage SPL2 modules](https://help.splunk.com/en/splunk-enterprise/search/spl2-search-manual/multiple-searches-in-an-spl2-module/manage-spl2-modules) and [Module permissions](https://help.splunk.com/en/splunk-enterprise/search/spl2-search-manual/modules-statements-and-views/module-permissions) in the Splunk documentation.\n\nSplunk Enterprise versions 10.2.x, 10.0.x, and 9.4.x are not affected."
                        }
                    ],
                    "value": "In Splunk Enterprise versions below 10.4.3, a user that holds a role with the list_spl2_modules capability could use SQL injection in SPL2 module filtering to access all relevant data available through the affected Representational State Transfer (REST) API, including private SPL2 module definitions belonging to other users. The vulnerability is possible because Splunk Enterprise and Splunk Cloud Platform do not parameterize user-supplied values before using them in database queries for SPL2 module filtering. For more information see Manage SPL2 modules (https://help.splunk.com/en/splunk-enterprise/search/spl2-search-manual/multiple-searches-in-an-spl2-module/manage-spl2-modules) and Module permissions (https://help.splunk.com/en/splunk-enterprise/search/spl2-search-manual/modules-statements-and-views/module-permissions) in the Splunk documentation.\n\nSplunk Enterprise versions 10.2.x, 10.0.x, and 9.4.x are not affected."
                }
            ],
            "references": [
                {
                    "url": "https://advisory.splunk.com/advisories/SVD-2026-1001"
                }
            ],
            "title": "Structured Query Language (SQL) Injection in the SPL2 Module Catalog in Splunk Enterprise",
            "datePublic": "2026-10-07T00:00:00.000Z",
            "problemTypes": [
                {
                    "descriptions": [
                        {
                            "lang": "en",
                            "type": "cwe",
                            "cweId": "CWE-89",
                            "description": "The software constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component."
                        }
                    ]
                }
            ],
            "source": {
                "advisory": "SVD-2026-1001",
                "discovery": ""
            },
            "providerMetadata": {
                "orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
                "shortName": "cisco",
                "dateUpdated": "2026-10-07T20:46:32.327Z"
            },
            "metrics": [
                {
                    "cvssV3_1": {
                        "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
                        "version": "3.1",
                        "baseScore": 6.5,
                        "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": "Jean-Michel Remi Boudreau",
                    "type": "reporter"
                }
            ]
        }
    }
}