GHSA-448J-JQ29-F2C7
Vulnerability from github – Published: 2026-11-19 21:31 – Updated: 2026-11-19 21:31In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a low-privileged user who holds the "power" Splunk role could inject arbitrary Search Processing Language (SPL) commands into a Classic Dashboard search. When another user opens the affected dashboard in Splunk Web, those injected commands execute with the viewing user's permissions, potentially allowing the low-privileged user to access stored credentials and write data to indexes. The vulnerability is possible because Splunk Enterprise does not correctly escape user-supplied content when it rewrites a search, which lets the rewritten search include additional SPL commands. The vulnerability requires another user to open the dashboard in Splunk Web. Consequently, a user who holds the "power" Splunk role should not be able to exploit the vulnerability at will. For more information see SPL safeguards for risky commands (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/best-practices-for-splunk-platform-security/spl-safeguards-for-risky-commands) and Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) in the Splunk documentation.
{
"affected": [],
"aliases": [
"CVE-2026-131183"
],
"database_specific": {
"cwe_ids": [
"CWE-116"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-11-19T20:17:30Z",
"severity": "MODERATE"
},
"details": "In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a low-privileged user who holds the \"power\" Splunk role could inject arbitrary Search Processing Language (SPL) commands into a Classic Dashboard search. When another user opens the affected dashboard in Splunk Web, those injected commands execute with the viewing user\u0027s permissions, potentially allowing the low-privileged user to access stored credentials and write data to indexes.\nThe vulnerability is possible because Splunk Enterprise does not correctly escape user-supplied content when it rewrites a search, which lets the rewritten search include additional SPL commands.\nThe vulnerability requires another user to open the dashboard in Splunk Web. Consequently, a user who holds the \"power\" Splunk role should not be able to exploit the vulnerability at will.\nFor more information see SPL safeguards for risky commands (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/best-practices-for-splunk-platform-security/spl-safeguards-for-risky-commands) and Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) in the Splunk documentation.",
"id": "GHSA-448j-jq29-f2c7",
"modified": "2026-11-19T21:31:46Z",
"published": "2026-11-19T21:31:46Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-131183"
},
{
"type": "WEB",
"url": "https://advisory.splunk.com/advisories/SVD-2026-1103"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N",
"type": "CVSS_V3"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.