CVE-2026-76264
Improper Authorization through the REST API in Splunk Enterprise
02 Description
Improper Authorization through the REST API in Splunk Enterprise
03 Exploitation and scoring
- Exploitation
- Assessed, none found. CISA's assessment recorded neither public exploit code nor evidence of exploitation when it was made.
- SSVC decision
- ExploitationnoneCISA recorded no public exploit code and no evidence of exploitation.
- AutomatablenoAt least one step from reconnaissance to exploitation cannot be reliably automated.
- Technical ImpactpartialSuccessful exploitation gives limited control of the vulnerable component.
- EPSS probability
- 0.22% probability of exploitation activity in the next 30 days.
- EPSS percentile
- Equal to or higher than the score of 12.7% of scored records. A rank, not a probability.
- NVD base score
- 4.3 (CVSS v3.x), scored by the NVD independently of the CNA.
- NVD CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
- NVD analysis status
- Analyzed. NVD last modified this record on 2026-10-14.
- Red Hat severity
- No Red Hat rating. Red Hat rates the CVEs that affect its products.
Exploit-prediction scores from FIRST. Independent scoring and analysis status from the NVD. Vendor severity from Red Hat. Exploitation assessment and catalog membership from CISA.
04 Metadata
- Published
- 2026-10-07 20:46Z21 DAYS AGO
- Last updated
- 2026-10-10 02:44Z19 DAYS AGO
- Reserved
- 2026-08-19
- Assigning CNA
- cisco
- Record state
- PUBLISHED
- Severity
- Medium (CVSS 4.3)
- CNA CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
- Weaknesses
- CWE-863Incorrect AuthorizationClass
- Data version
- 5.2
- Document digest
- 49d2989f93785f1fbaaf3c24726dfe655cfbaaa6be2d59ab07c2e0430c7cb1a3
05 Affected products
06 References
- advisory.splunk.comhttps://advisory.splunk.com/advisories/SVD-2026-1001
07 Remediation
Upgrade Splunk Enterprise to versions 10.4.3, 10.2.7, 10.0.10, and 9.4.15, or higher. After upgrading, set `scripted_lookup_raw_write_enforcement = block` in the `limits.conf` configuration file under [lookup], and then restart Splunk Enterprise. For more information see [Configuration file reference](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/configuration-file-reference/10.2.7-configuration-file-reference/limits%2Econf) in the Splunk documentation.