Splunk Enterprise unauthorized changes to HTML views via REST API
- Exploited
- No known exploitation
- Fix
- Fixed in 10.4.4, 10.2.8, 10.0.11, 9.4.17
- Who is exposed
- Not reported
Summary
Splunk Enterprise has a missing-authorization flaw in its REST API that lets a logged-in user with the edit_own_objects capability, but without edit_view_html, create or modify private HTML-based views. The attacker can reach it remotely over the network with low-privilege credentials, and the impact is limited to integrity, since the user can change those views.
Written by a model
Original description
In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.17, a user that holds a role with the edit_own_objects capability but does not hold the edit_view_html capability could create or modify a private Hypertext Markup Language (HTML) view through the Representational State Transfer (REST) API. The vulnerability is possible because the REST API applies the edit_own_objects capability when it creates or modifies private HTML-based views instead of requiring the edit_view_html capability. For more information see Define roles on the Splunk platform with capabilities (help.splunk.com/
What to do
Upgrade to a fixed version: 10.4.4, 10.2.8, 10.0.11, 9.4.17.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-131176 (Missing Authorization for HTML-Based Views through the REST API in Splunk Enterprise), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-131176 (entry last updated 2026-11-19):
Affected:
- Splunk Splunk Enterprise: from 10.4, fixed in 10.4.4; from 10.2, fixed in 10.2.8; from 10.0, fixed in 10.0.11; from 9.4, fixed in 9.4.17
Fixed versions: 10.4.4, 10.2.8, 10.0.11, 9.4.17.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-131176 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131176 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://advisory.splunk.com/advisories/SVD-2026-1103
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-131176
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131176"}.Affected versions
- Splunk Splunk EnterpriseFrom 10.4 · fixed in 10.4.4; From 10.2 · fixed in 10.2.8; From 10.0 · fixed in 10.0.11; From 9.4 · fixed in 9.4.17
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.3/10CVSS 4.3
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 26 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | advisory.splunk.com · advisories/SVD-2026-1103 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-131176 |
| Record | NVD · CVE-2026-131176 |
Questions about CVE-2026-131176
Is CVE-2026-131176 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-131176?
Splunk Enterprise: from 10.4 before 10.4.4; from 10.2 before 10.2.8; from 10.0 before 10.0.11; from 9.4 before 9.4.17.
Source: cve.now feed data
How do I fix CVE-2026-131176?
Upgrade to a fixed version: 10.4.4, 10.2.8, 10.0.11, 9.4.17.
Source: cve.now feed data
Related
- CVE-2026-131236SPL Injection through Splunk Web Workflow Actions in Splunk Enterprise Security
- CVE-2026-131218SPL Injection through the Mission Control REST API in Splunk Enterprise Security
- CVE-2026-131239SPL Injection through the System Update Status Report in Splunk Enterprise Security
- CVE-2026-131222Privilege Escalation through Asset and Identity Management in Splunk Enterprise Security
- CVE-2026-131238Search Processing Language (SPL) Injection through the Secure Sockets Layer Search Dashboard in Splunk Enterprise Security
- CVE-2026-131232SPL Injection through the Vulnerability Scan Details Splunk Web Dashboard in Splunk Enterprise Security
No corrections so far. Something wrong on this page? Report an error.