{
  "id": "CVE-2026-76322",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-76322",
  "published_at": "2026-08-19T21:34:27.915Z",
  "title": "SPL Injection through Dashboard Studio Search Query Options in Splunk Enterprise",
  "vendor": "Splunk",
  "product": "Splunk Enterprise",
  "cvss": {
    "score": 8,
    "source": "nvd",
    "vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user who holds the \"user\" Splunk role could craft a Dashboard Studio dashboard that runs attacker-controlled Search Processing Language (SPL) for another authenticated user. The attacker-controlled SPL could access all relevant data and affect system integrity and availability. The vulnerability is possible because Dashboard Studio does not consistently enforce the expected app-visibility authorization boundary before dashboard search query options reach search dispatch. The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The user who holds the \"user\" Splunk role should not be able to exploit the vulnerability at will. For more information see Create search-based visualizations with ds.search (https://help.splunk.com/en/splunk-enterprise/create-dashboards-and-reports/dashboard-studio/10.4/use-data-sources/create-search-based-visualizations-with-ds.search) in the Splunk documentation.",
  "cwe": "CWE-862",
  "cpes": [
    "cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*"
  ],
  "cvss_by_source": {
    "cna": 6.7,
    "nvd": 8
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Splunk",
        "product": "Splunk Enterprise",
        "ranges": [
          "\u003e= 10.4, \u003c 10.4.2",
          "\u003e= 10.2, \u003c 10.2.6",
          "\u003e= 10.0, \u003c 10.0.9",
          "\u003e= 9.4, \u003c 9.4.14"
        ],
        "fixed_in": [
          "10.4.2",
          "10.2.6",
          "10.0.9",
          "9.4.14"
        ]
      }
    ],
    "solutions": [
      "Upgrade Splunk Enterprise to versions 10.4.2, 10.2.6, 10.0.9, and 9.4.14, or higher."
    ],
    "upgrade": [
      "Upgrade Splunk Enterprise to 10.4.2 or 10.2.6 or 10.0.9 or 9.4.14 or later."
    ],
    "workarounds": [
      "The vulnerability affects instances with Splunk Web turned on. Turning Splunk Web off is a possible workaround. See [Disable unnecessary Splunk Enterprise components](https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.2/install-splunk-enterprise-securely/disable-unnecessary-splunk-enterprise-components) and the [web.conf](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/configuration-file-reference/10.2.0-configuration-file-reference/web.conf) configuration specification file for more information on turning off Splunk Web."
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
