Skip to content
Fencer Intel
medium 4.3

CVE-2026-131191 json

Sensitive Information Disclosure through the Deployment Server REST API in Splunk Enterprise

published 6h ago modified 6h ago also EUVD-2026-130586

cvss
4.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who does not hold the "admin" or "power" Splunk roles could read private index configuration values for other users through the deployment server Representational State Transfer (REST) API. The deployment server REST API does not limit a supplied repository location to configured deployment repositories before it reads indexes.conf stanzas.

Patch / fix

  • Splunk Splunk Enterprise 9.4.17, 10.0.12, 10.2.9, 10.4.5

Is CVE-2026-131191 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
CNA 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
NVD 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected products

  • Splunk Splunk Enterprise

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.