splunk-otel-javaagent: Unsafe deserialization in RMI instrumentation may lead to Remote Code Execution

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

9.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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: 1. Splunk Distribution of OpenTelemetry Java is attached as a Java agent (-javaagent) 2. An RMI endpoint is network-reachable (e.g. JMX remote port, an RMI registry, or any application-exported RMI service) 3. 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: References Advisory in OpenTelemetry Instrumentation for Java

Published by the source

26 Mar 2026, 17:22 UTC

Last modified by the source

26 Mar 2026, 17:22 UTC

Source last checked

26 Oct 2026, 16:44 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-h8w2-rv57-vc6f

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-h8w2-rv57-vc6f

Advisory: splunk-otel-javaagent: Unsafe deserialization in RMI instrumentation may lead to Remote Code Execution
IDs: GHSA-h8w2-rv57-vc6f
Record: https://patchnext.com/advisories/ghsa-h8w2-rv57-vc6f (revision 1, source checked 26 Oct 2026, 16:44 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.splunk:splunk-otel-javaagent 2.26.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.splunk:splunk-otel-javaagent: affected < 2.26.1; fixed in 2.26.1

## Suggested inspection (read-only)
- Maven com.splunk:splunk-otel-javaagent: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.splunk:splunk-otel-javaagent.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-h8w2-rv57-vc6f (GitHub-reviewed advisory GHSA-h8w2-rv57-vc6f lists affected ranges: Maven com.splunk:splunk-otel-javaagent >=0 <2.26.1)

Commands are suggestions: review each one before running it.