GHSA-28F2-3P4C-88J9
Vulnerability from github – Published: 2026-11-19 21:31 – Updated: 2026-11-19 21:31In Splunk Enterprise Security versions below 8.7.0, a user who can influence event values that populate an affected data model based on the Common Information Model could cause attacker-controlled values to appear in an affected Dashboard Studio view. Another authenticated user could later click a corresponding row in that view. Splunk Enterprise Security could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who clicked the row. The commands could access or modify some data available to the user who clicked the row. The vulnerability is possible because affected Dashboard Studio drilldowns do not safely quote data model values before including them in searches. For more information see Users and roles for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.7/installation/users-and-roles-for-splunk-enterprise-security) and Create a dashboard in Dashboard Studio (https://help.splunk.com/en/splunk-enterprise/create-dashboards-and-reports/dashboard-studio/10.2/create-a-dashboard-in-dashboard-studio/create-a-dashboard-in-dashboard-studio) in the Splunk documentation.
{
"affected": [],
"aliases": [
"CVE-2026-131220"
],
"database_specific": {
"cwe_ids": [
"CWE-74"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-11-19T20:17:36Z",
"severity": "MODERATE"
},
"details": "In Splunk Enterprise Security versions below 8.7.0, a user who can influence event values that populate an affected data model based on the Common Information Model could cause attacker-controlled values to appear in an affected Dashboard Studio view. Another authenticated user could later click a corresponding row in that view. Splunk Enterprise Security could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who clicked the row. The commands could access or modify some data available to the user who clicked the row.\nThe vulnerability is possible because affected Dashboard Studio drilldowns do not safely quote data model values before including them in searches.\nFor more information see Users and roles for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.7/installation/users-and-roles-for-splunk-enterprise-security) and Create a dashboard in Dashboard Studio (https://help.splunk.com/en/splunk-enterprise/create-dashboards-and-reports/dashboard-studio/10.2/create-a-dashboard-in-dashboard-studio/create-a-dashboard-in-dashboard-studio) in the Splunk documentation.",
"id": "GHSA-28f2-3p4c-88j9",
"modified": "2026-11-19T21:31:51Z",
"published": "2026-11-19T21:31:51Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-131220"
},
{
"type": "WEB",
"url": "https://advisory.splunk.com/advisories/SVD-2026-1106"
}
],
"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:L",
"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.