GHSA-h8w2-rv57-vc6f — splunk-otel-javaagent
GHSA-h8w2-rv57-vc6f is a remote code execution vulnerability in com.splunk:splunk-otel-javaagent. A fix is available for com.splunk:splunk-otel-javaagent — see the affected versions and patch details below.
splunk-otel-javaagent: Unsafe deserialization in RMI instrumentation may lead to Remote Code Execution
Real-World Exposure
com.splunk:splunk-otel-javaagentReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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
Impact
Arbitrary remote code execution with the privileges of the user running the instrumented JVM.
Recommendation
Upgrade to version 2.26.1 or later.
Workarounds
Set the following system property to disable the RMI integration:
-Dotel.instrumentation.rmi.enabled=false
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.splunk:splunk-otel-javaagent | all versions | 2.26.1com.splunk:splunk-otel-javaagent:2.26.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.splunk:splunk-otel-javaagent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.splunk:splunk-otel-javaagent to 2.26.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h8w2-rv57-vc6f is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-h8w2-rv57-vc6f can be triaged on real exposure rather than presence alone.
Tailored to GHSA-h8w2-rv57-vc6f. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-h8w2-rv57-vc6f in your dependencies?
O3 Security finds GHSA-h8w2-rv57-vc6f across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.