Skip to content
High 7.5

Authentication Bypass through the RapidDiag REST API in Splunk Enterprise

CVE-2026-131190 First seen on SecPulse

Summary

In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could access RapidDiag process metadata and log file inventory information through the Representational State Transfer (REST) API.
The vulnerability is possible because certain RapidDiag REST API endpoin...

Affected packages

PackageAffected → Fixed
SplunkSplunk Enterprise
≥ 10.4, < 10.4.5→ 10.4.5
≥ 10.2, < 10.2.9→ 10.2.9
≥ 10.0, < 10.0.12→ 10.0.12
≥ 9.4, < 9.4.17→ 9.4.17
Original description The description as published by the source.

In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could access RapidDiag process metadata and log file inventory information through the Representational State Transfer (REST) API.
The vulnerability is possible because certain RapidDiag REST API endpoints accept a factory-default shared key for node authentication, which lets requests bypass Splunk user authentication.
For more information see Using RapidDiag (https://help.splunk.com/en/splunk-enterprise/administer/troubleshoot/9.0/contact-splunk-support/using-rapiddiag) and Secure Splunk Enterprise services with pass4SymmKey (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.0/secure-distributed-and-clustered-splunk-environments/secure-splunk-enterprise-services-with-pass4symmkey) in the Splunk documentation.

Source: CVE.org (CVE Program・cvelistV5) NVD

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details