Skip to content

← Public intelligence

Maven package

io.opentelemetry.javaagent:opentelemetry-javaagent

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

3 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.5MavenAmendedPublished

    OpenTelemetry Java Instrumentation: JDBC Auto-Instrumentation Logging Clear-Text Passwords

    CVE-2026-54704 · GHSA-rwqx-fvqh-6wm4

    Affected
    • Maven io.opentelemetry.javaagent:opentelemetry-javaagent < 2.28.0-alpha
    Fixed in
    2.28.0-alpha· Vendor fix available
    Issue
    OpenTelemetry Java Instrumentation JDBC auto-instrumentation may fail to sanitize passwords in SQL CONNECT statements when the password is double-quoted. As a result, clear-text database passwords can be added to trace span attributes and exported to observability backends.

    Recommended action: Upgrade to 2.28.0-alpha (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  2. Medium, CVSS 5.3MavenAmendedPublished

    OpenTelemetry Javaagent RMI context propagation allows resource exhaustion

    CVE-2026-54712 · GHSA-fq3f-m5qm-99f5

    Affected
    • Maven io.opentelemetry.javaagent:opentelemetry-javaagent < 2.27.0
    Fixed in
    2.27.0· Vendor fix available
    Issue
    The RMI context propagation payload reader limits the number of context entries but does not limit the aggregate size of the strings read from the stream. An attacker who can reach an RMI endpoint on an instrumented JVM can send an oversized context propagation payload. This can cause excessive memory allocation while the JVM reads the payload, potentially leading to denial of service. The issue affects only deployments where RMI instrumentation is enabled and an RMI endpoint is network-reachable.

    Recommended action: Upgrade to 2.27.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  3. Critical, CVSS 9.3MavenPublished

    OpenTelemetry: Unsafe Deserialization in RMI Instrumentation may Lead to Remote Code Execution

    CVE-2026-33701 · GHSA-xw7x-h9fj-p2c7

    Affected
    • Maven io.opentelemetry.javaagent:opentelemetry-javaagent < 2.26.1
    Fixed in
    2.26.1· Vendor fix available
    Issue
    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. OpenTelemetry Java instrumentation 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: Credits This vulnerability was responsibly disclosed in coordination with Datadog.

    Recommended action: Upgrade to 2.26.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →