CVE-2026-33728: dd-trace-java: Unsafe deserialization in RMI instrumentation may lead to remote code execution

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
• EPSS 1.0%, percentile 62: FIRST’s model estimates a 1.0% chance of exploitation activity in the next 30 days, higher than 62% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
• Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
• Only applies if your dependency tree includes com.datadoghq:dd-java-agent (Maven) >= 0.40.0, < 1.60.3, fixed in 1.60.3. Check your lockfile, including transitive dependencies.

What it is

dd-trace-java is a Datadog APM client for Java. In versions of dd-trace-java 0.40.0 through prior to 1.60.2, 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: First, dd-trace-java is attached as a Java agent (-javaagent) on Java 16 or earlier. Second, a JMX/RMI port has been explicitly configured via -Dcom.sun.management.jmxremote.port and is network-reachable, Third, a gadget-chain-compatible library is present on the classpath. For JDK >= 17, no action is required, but upgrading is strongly encouraged. For JDK >= 8u121

From the GitHub advisory

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

Workarounds Set the following environment variable to disable the RMI integration: DDINTEGRATIONRMIENABLED=false

Credits This vulnerability was responsibly disclosed by Mohamed Amine ait Ouchebou (mrecho) (Indiesecurity) via the Datadog bug bounty program.

Weakness type: CWE-502.

Product: com.datadoghq:dd-java-agent (Maven) · Assigned by: GitHub_M · Published: 2026-03-27

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Attack requirements: none
• Privileges required: none (no login)
• User interaction: none

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
• CISA SSVC assessment: exploitation none, automatable yes, technical impact total.
• FIRST EPSS (model of 2026-10-21): 0.99% probability of exploitation activity in the next 30 days; percentile 62.

Timeline

• 2026-03-26 — GitHub-reviewed advisory GHSA-579q-h82j-r5v2 published (critical)
• 2026-03-27 — CVE record last updated
• 2026-03-27 — CVE record published by GitHub_M

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

1. GitHub Advisory GHSA-579q-h82j-r5v2 github.com
2. CVE.org record CVE-2026-33728 cve.org
3. NVD entry CVE-2026-33728 nvd.nist.gov

Other references from the CVE record and advisory

1. github.com github.com
2. github.com github.com

Critical Maven advisories · Today’s Security Digest