Summary
splunk-otel-javaagent: Unsafe deserialization in RMI instrumentation may lead to Remote Code Execution
In versions prior to 2.26.1, the RMI instrumentation registered a custom endpoint that deserialized incoming data without applying serialization filters. An attacker with network access to a JMX or RMI port on an instrumented JVM could exploit this to potentially achieve remote code execution. All three of the following conditions must be true to exploit this vulnerability:
- Splunk Distribution of OpenTelemetry Java is attached as a Java agent (
-javaagent) - An RMI endpoint is network-reachable (e.g. JMX remote port, an RMI registry, or any application-exported RMI service)
- A gadget-chain-compatible library is present on the classpath
Workarounds
Set the following system property to disable the RMI integration:
-Dotel.instrumentation.rmi.enabled=false
References
Impact
Arbitrary remote code execution with the privileges of the user running the instrumented JVM.
Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect. Typical impact: arbitrary code execution or logic abuse.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Upgrade to version 2.26.1 or later.
Frequently Asked Questions
- What is GHSA-H8W2-RV57-VC6F? GHSA-H8W2-RV57-VC6F is a critical-severity insecure deserialization vulnerability in com.splunk:splunk-otel-javaagent (maven), affecting versions < 2.26.1. It is fixed in 2.26.1. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
- Which versions of com.splunk:splunk-otel-javaagent are affected by GHSA-H8W2-RV57-VC6F? com.splunk:splunk-otel-javaagent (maven) versions < 2.26.1 is affected.
- Is there a fix for GHSA-H8W2-RV57-VC6F? Yes. GHSA-H8W2-RV57-VC6F is fixed in 2.26.1. Upgrade to this version or later.
- Is GHSA-H8W2-RV57-VC6F exploitable, and should I be worried? Whether GHSA-H8W2-RV57-VC6F is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-H8W2-RV57-VC6F is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-H8W2-RV57-VC6F? Upgrade
com.splunk:splunk-otel-javaagentto 2.26.1 or later.