Unsafe deserialization in dd-trace-java RMI instrumentation may lead to remote code execution
Critical9.3CVE-2026-33728 · Published Mar 23, 2026 · updated Mar 30, 2026
In versions of dd-trace-java prior to 1.60.3, the RMI instrumentation registered a custom endpoint that deserialized incoming data without applying serialization filters. On JDK version 16 and earlier, 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. dd-trace-java is attached as a Java agent (`-javaagent`) on Java 16 or earlier 2. A JMX/RMI port has been explicitly configured via `-Dcom.sun.management.jmxremote.port` and is network-reachable 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 - For JDK >= 17: No action is required, but upgrading is strongly encouraged. - For JDK >= 8u121 < JDK 17: Upgrade to dd-trace-java version 1.60.3 or later. - For JDK < 8u121 and earlier where serialization filters are not available, apply the workaround described below. ### Workarounds Set the following environment variable to disable the RMI integration: `DD_INTEGRATION_RMI_ENABLE...
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| com.datadoghq:dd-java-agent Maven | >= 0.40.0, < 1.60.3 | 1.60.3 |
Details and references
In versions of dd-trace-java prior to 1.60.3, the RMI instrumentation registered a custom endpoint that deserialized incoming data without applying serialization filters. On JDK version 16 and earlier, 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. dd-trace-java is attached as a Java agent (`-javaagent`) on Java 16 or earlier 2. A JMX/RMI port has been explicitly configured via `-Dcom.sun.management.jmxremote.port` and is network-reachable 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 - For JDK >= 17: No action is required, but upgrading is strongly encouraged. - For JDK >= 8u121 < JDK 17: Upgrade to dd-trace-java version 1.60.3 or later. - For JDK < 8u121 and earlier where serialization filters are not available, apply the workaround described below. ### Workarounds Set the following environment variable to disable the RMI integration: `DD_INTEGRATION_RMI_ENABLED=false` ### Credits This vulnerability was responsibly disclosed by Mohamed Amine ait Ouchebou (mrecho) (Indiesecurity) via the Datadog bug bounty program.
- 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
- Severity from
- GitHub (reviewed advisory)
More Datadog advisories
All Datadog| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Jun 5 | Improper parsing of W3C baggage headers may lead to DoS | High7.5 | 2.8.1+1 more |
| Jun 5 | Improper parsing of W3C baggage headers may lead to DoS | High7.5 | 5.100.0 |
| Jun 5 | Improper parsing of W3C baggage headers may lead to DoS | High7.5 | 3.43.0+1 more |
| Jun 5 | Improper parsing of W3C baggage headers may lead to DoS | High7.5 | 4.8.2 |
| Jun 5 | Improper parsing of W3C baggage headers may lead to DoS | High7.5 | 1.62.0 |
| Jun 5 | Improper parsing of W3C baggage headers may lead to DoS | High7.5 | 1.19.2 |