Description
In Splunk Enterprise versions below 10.2.0, 10.0.2, 9.4.7, 9.3.9, and 9.2.11, a user of a Splunk Search Head Cluster (SHC) deployment who holds a role with access to the Splunk `_internal` index could view the RSA `accessKey` value from the [<u>Authentication.conf</u> ](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/configuration-file-reference/10.2.0-configuration-file-reference/authentication.conf)file, in plain text.
Published: 2026-02-18
Score: 6.8 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Information Disclosure
Action: Apply Patch
AI Analysis

Impact

In Splunk Enterprise versions prior to 10.2.0, 10.0.2, 9.4.7, 9.3.9 and 9.2.11, a user with a role that allows access to the internal index can read the RSA accessKey value from the Authentication.conf file in plain text. The flaw is a classic information‑disclosure weakness.

Affected Systems

Splunk Enterprise deployments that use a Search Head Cluster and run versions below 10.2.0, 10.0.2, 9.4.7, 9.3.9 or 9.2.11 are impacted. The vulnerability involves the internal index stored in the cluster and the Authentication.conf configuration file.

Risk and Exploitability

The CVSS base score is 6.8, indicating a moderate severity. The EPSS score is below 1 percent, suggesting a very low likelihood of exploitation. The vulnerability is not listed in the CISA KEV catalog. An attacker would need to possess a role with read access to the internal index; this is typically a privileged role within the organization.

Generated by OpenCVE AI on April 18, 2026 at 11:56 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Splunk Enterprise to version 10.2.0 or later, or to the latest minor release of 10.0, 9.4, 9.3, or 9.2 that contains the fix
  • Restrict the Splunk role that can access the internal index so that only trusted administrators have that permission
  • Regenerate the RSA accessKey in Authentication.conf and ensure the file is protected from unauthorized read access

Generated by OpenCVE AI on April 18, 2026 at 11:56 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 23 Feb 2026 14:45:00 +0000

Type Values Removed Values Added
First Time appeared Splunk splunk
CPEs cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*
Vendors & Products Splunk splunk

Thu, 19 Feb 2026 10:30:00 +0000

Type Values Removed Values Added
First Time appeared Splunk
Splunk splunk Enterprise
Vendors & Products Splunk
Splunk splunk Enterprise

Wed, 18 Feb 2026 18:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Wed, 18 Feb 2026 17:30:00 +0000

Type Values Removed Values Added
Description In Splunk Enterprise versions below 10.2.0, 10.0.2, 9.4.7, 9.3.9, and 9.2.11, a user of a Splunk Search Head Cluster (SHC) deployment who holds a role with access to the Splunk `_internal` index could view the RSA `accessKey` value from the [<u>Authentication.conf</u> ](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/configuration-file-reference/10.2.0-configuration-file-reference/authentication.conf)file, in plain text.
Title Sensitive Information Disclosure in "_internal" index in Splunk Enterprise
Weaknesses CWE-532
References
Metrics cvssV3_1

{'score': 6.8, 'vector': 'CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H'}


Subscriptions

Splunk Splunk Splunk Enterprise
cve-icon MITRE

Status: PUBLISHED

Assigner: cisco

Published:

Updated: 2026-02-26T14:44:16.319Z

Reserved: 2025-10-08T11:59:15.382Z

Link: CVE-2026-20142

cve-icon Vulnrichment

Updated: 2026-02-18T17:43:31.731Z

cve-icon NVD

Status : Analyzed

Published: 2026-02-18T18:24:28.053

Modified: 2026-02-23T14:44:34.597

Link: CVE-2026-20142

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-04-18T12:00:05Z

Weaknesses