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

Advisory record · `GHSA-h8w2-rv57-vc6f`

- **Identifiers:** `GHSA-h8w2-rv57-vc6f`
- **State:** Confirmed
- **Severity:** CVSS 4.0, no score published
- **Critical:** No
- **Weakness (CWE):** [CWE-502](https://cwe.mitre.org/data/definitions/502.html) · [CWE-1395](https://cwe.mitre.org/data/definitions/1395.html)
- **Tags:** [Insecure deserialization](https://agentprime.io/advisories/tag/deserialization.md) · [CWE-1395](https://agentprime.io/advisories/tag/cwe-1395.md)
- **Published:** 26 Mar 2026
- **Updated:** 26 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 26 Mar 2026, 17:22 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `com.splunk:splunk-otel-javaagent` (Maven): affected `<2.26.1`; fixed in `2.26.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The splunk-otel-javaagent package, versions before 2.26.1, has an unsafe deserialization flaw in its RMI instrumentation. An attacker with network access to a JMX or RMI port on an instrumented JVM, plus a compatible gadget-chain library on the classpath, could achieve remote code execution. Upgrade to 2.26.1 or later; a workaround is to disable the RMI integration with a system property.

Written 3 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- Score not published, CVSS 4.0: `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`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 14:20 UTC: First seen by agentprime
- 31 Oct 2026, 14:20 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-h8w2-rv57-vc6f)

## Sources

- [GitHub Advisory Database: GHSA-h8w2-rv57-vc6f](https://github.com/advisories/GHSA-h8w2-rv57-vc6f)
- [OSV: GHSA-h8w2-rv57-vc6f](https://osv.dev/vulnerability/GHSA-h8w2-rv57-vc6f)
- <https://github.com/open-telemetry/opentelemetry-java-instrumentation/security/advisories/GHSA-xw7x-h9fj-p2c7>
- <https://github.com/signalfx/splunk-otel-java/security/advisories/GHSA-h8w2-rv57-vc6f>
- <https://github.com/signalfx/splunk-otel-java>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-h8w2-rv57-vc6f>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-h8w2-rv57-vc6f/>. Everything for agents: <https://agentprime.io/llms.txt>.