Is CVE-2026-54704 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-54704 being exploited in the wild.

How severe is CVE-2026-54704?

Medium severity, with a CVSS score of 6.5, published 1 July 2026.

Which products and versions are affected?

io.opentelemetry.javaagent:opentelemetry-javaagent (Maven) < 2.28.0-alpha, ECOSYSTEM:introduced=0,fixed=2.28.0-alpha; Opentelemetry-Java-Instrumentation < 2.28.0; Opentelemetry-Javaagent < 2.28.0-alpha.

Is there a fix for CVE-2026-54704?

Yes. io.opentelemetry.javaagent:opentelemetry-javaagent (Maven): upgrade to 2.28.0-alpha or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-54704 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-54704?

Check whether you run io.opentelemetry.javaagent:opentelemetry-javaagent (Maven), Opentelemetry-Java-Instrumentation or Opentelemetry-Javaagent at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-54704: OpenTelemetry Java Instrumentation information disclosure in JDBC auto-instrumentation

Q: Is there a fix for CVE-2026-54704?

Yes. io.opentelemetry.javaagent:opentelemetry-javaagent (Maven): upgrade to 2.28.0-alpha or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-54704 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-54704?

Check whether you run io.opentelemetry.javaagent:opentelemetry-javaagent (Maven), Opentelemetry-Java-Instrumentation or Opentelemetry-Javaagent at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-54704 · Severity: medium · CVSS 6.5 · Published 2026-07-01

OpenTelemetry Java Instrumentation, a tool used to monitor application performance, contains a flaw that may accidentally record database passwords in plain text. This occurs when database connection strings use double quotes for passwords, causing the sensitive information to be stored in monitoring logs and exported to external observability platforms. If an unauthorized person gains access to these logs or the monitoring backend, they could obtain credentials to access the organization's databases.

Technologies: io.opentelemetry.javaagent:opentelemetry-javaagent (Maven), Opentelemetry-Java-Instrumentation, Opentelemetry-Javaagent. Vendors: Maven, Opentelemetry.

Quick answers

Is CVE-2026-54704 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-54704 being exploited in the wild.
How severe is CVE-2026-54704?: Medium severity, with a CVSS score of 6.5, published 1 July 2026.
Which products and versions are affected?: io.opentelemetry.javaagent:opentelemetry-javaagent (Maven) < 2.28.0-alpha, ECOSYSTEM:introduced=0,fixed=2.28.0-alpha; Opentelemetry-Java-Instrumentation < 2.28.0; Opentelemetry-Javaagent < 2.28.0-alpha.
Is there a fix for CVE-2026-54704?: Yes. io.opentelemetry.javaagent:opentelemetry-javaagent (Maven): upgrade to 2.28.0-alpha or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-54704 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-54704?: Check whether you run io.opentelemetry.javaagent:opentelemetry-javaagent (Maven), Opentelemetry-Java-Instrumentation or Opentelemetry-Javaagent at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

io.opentelemetry.javaagent:opentelemetry-javaagent (Maven): upgrade to 2.28.0-alpha or later

# set io.opentelemetry.javaagent:opentelemetry-javaagent to 2.28.0-alpha in your pom.xml or build.gradle

Technical details

A vulnerability in the JDBC auto-instrumentation component of OpenTelemetry Java Instrumentation (CWE-532) fails to properly sanitize sensitive information during SQL CONNECT statement processing. Specifically, when a password in a connection string is enclosed in double quotes, the sanitization logic is bypassed. This results in clear-text database credentials being recorded as span attributes within traces. These traces are then exported to configured observability backends, potentially exposing credentials to any user with access to the telemetry data. The issue is fixed in version 2.28.0-alpha.

Affected products

OpenTelemetry opentelemetry-javaagent < 2.28.0-alpha

Identifiers

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

Timeline

2026-06-09: patched: Initial patch released in version 2.28.0-alpha
2026-07-01: advisory: NVD publication date
2026-07-29: disclosed: GitHub Advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.