dbcve.org
Dd Trace JavaApplication · Datadog

CVE-2026-33728

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-27
Fix available
A fix is available. Upgrade to 1.60.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 < 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. The workaround is to set the following environment variable to disable the RMI integration: `DD_INTEGRATION_RMI_ENABLED=false`.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

dd-trace-java versions 0.40.0 through 1.60.2 have a deserialization vulnerability in the RMI instrumentation. The custom RMI endpoint deserializes incoming data without applying serialization filters, allowing remote code execution on JDK 16 and earlier when JMX/RMI ports are network-accessible and a gadget-chain-compatible library exists on the classpath.

MitigationUpgrade dd-trace-java to version 1.60.3 or later for JDK 8u121 through JDK 16; for older JDK versions, set DD_INTEGRATION_RMI_ENABLED=false to disable the vulnerable RMI integration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Dd Trace JavaApplication
Affected:>= 0.40.0, < 1.60.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify dd-trace-java version
    Locate the dd-trace-java library in your application classpath or dependency management system (Maven pom.xml, Gradle build file, or JAR manifest). Check the version number.
    Affected if The installed version falls within 0.40.0 through 1.60.2 (inclusive).
  2. Verify JDK version
    Run `java -version` or check the JAVA_HOME environment variable to determine the JDK version in use.
    Affected if The JDK is version 16 or earlier.
  3. Confirm RMI integration is enabled
    Check for the environment variable DD_INTEGRATION_RMI_ENABLED or any configuration that enables the RMI instrumentation. If not set, the default is typically enabled.
    Affected if DD_INTEGRATION_RMI_ENABLED is not set to false, or the RMI integration is explicitly enabled.
  4. Assess network exposure of JMX/RMI ports
    Review your network configuration and firewall rules to determine if JMX/RMI ports (typically port 9010, 9011, or dynamic RMI ports) are accessible from untrusted networks.
    Affected if JMX/RMI ports are exposed to network-accessible interfaces rather than localhost only.

Your environment is affected if you have dd-trace-java version 0.40.0-1.60.2 running on JDK 16 or earlier with the RMI integration enabled and network-accessible JMX/RMI ports.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.60.3 or later
Fixed in 1.60.3
Interim mitigation

Upgrade dd-trace-java to version 1.60.3 or later for JDK 8u121 through JDK 16; for older JDK versions, set DD_INTEGRATION_RMI_ENABLED=false to disable the vulnerable RMI integration.

Recommended fix High confidence

dd-trace-java version 1.60.3 or later

  1. Upgrade dd-trace-java to version 1.60.3 or later by updating your build configuration (Maven/Gradle) or the javaagent JAR file
  2. If using JDK < 8u121 where serialization filters are unavailable as an additional precaution, set the environment variable DD_INTEGRATION_RMI_ENABLED=false to disable the RMI integration
  3. Restart the JVM to apply the changes
  4. Verify the application starts successfully and APM functionality is working as expected
Caveat Review release notes for any breaking changes between your current version and 1.60.3; test thoroughly in a non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dd Trace Java Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,880
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,608.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33728 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33728 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data