GHSA-5J4C-H4G3-J2Q3
Vulnerability from github – Published: 2026-11-19 21:31 – Updated: 2026-11-19 21:31In Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a low-privileged user who does not hold the "admin" or "power" Splunk roles could inject a malicious script into the name of a private saved search. If another user subsequently enables, disables, or edits the corresponding platform alert in the Monitoring Console, the injected script executes within that user's browser session, potentially allowing the low-privileged user to view sensitive information or modify data in Splunk Enterprise. The vulnerability is possible because the Monitoring Console does not safely handle saved-search names in the platform alert workflow. For more information see Enable and configure platform alerts (https://help.splunk.com/en/splunk-enterprise/administer/monitor/10.4/configure-the-monitoring-console/enable-and-configure-platform-alerts) and About configuring role-based user access (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/about-configuring-role-based-user-access) in the Splunk documentation.
{
"affected": [],
"aliases": [
"CVE-2026-131184"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-11-19T20:17:30Z",
"severity": "MODERATE"
},
"details": "In Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a low-privileged user who does not hold the \"admin\" or \"power\" Splunk roles could inject a malicious script into the name of a private saved search. If another user subsequently enables, disables, or edits the corresponding platform alert in the Monitoring Console, the injected script executes within that user\u0027s browser session, potentially allowing the low-privileged user to view sensitive information or modify data in Splunk Enterprise.\nThe vulnerability is possible because the Monitoring Console does not safely handle saved-search names in the platform alert workflow.\nFor more information see Enable and configure platform alerts (https://help.splunk.com/en/splunk-enterprise/administer/monitor/10.4/configure-the-monitoring-console/enable-and-configure-platform-alerts) and About configuring role-based user access (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/about-configuring-role-based-user-access) in the Splunk documentation.",
"id": "GHSA-5j4c-h4g3-j2q3",
"modified": "2026-11-19T21:31:46Z",
"published": "2026-11-19T21:31:46Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-131184"
},
{
"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:H/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.