dbcve.org
Opentelemetry Instrumentation For JavaApplication · Linuxfoundation

CVE-2026-54704

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-01
Fix available
A fix is available. Upgrade to 2.28.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 7 weeks old

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
OpenTelemetry Java Instrumentation provides OpenTelemetry auto-instrumentation and instrumentation libraries for Java. In versions prior to 2.28.0, the 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. This issue has been fixed in version 2.28.0.

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

The OpenTelemetry Java Instrumentation JDBC auto-instrumentation fails to sanitize passwords in SQL CONNECT statements when the password is double-quoted. This causes clear-text database passwords to be captured in trace span attributes and exported to observability backends, creating a credential exposure risk.

MitigationUpgrade OpenTelemetry Java Instrumentation to version 2.28.0 or later to patch the password sanitization failure in JDBC auto-instrumentation.

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
Opentelemetry Instrumentation For JavaApplication
Affected:< 2.28.0

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Locate the OpenTelemetry Java Instrumentation agent JAR
    Search your application deployment for 'opentelemetry-javaagent.jar' or similar OpenTelemetry Java agent files. Check application startup scripts, lib directories, or container images for the agent JAR.
    Affected if The agent JAR exists in your deployment and its version is below 2.28.0
  2. Identify the installed OpenTelemetry Java agent version
    Run 'java -jar <path-to-opentelemetry-javaagent.jar> --version' or check the filename/version in the JAR manifest (META-INF/MANIFEST.MF) for the 'Implementation-Version' attribute.
    Affected if The version is present and less than 2.28.0
  3. Confirm JDBC auto-instrumentation is active
    Review your application startup arguments for '-javaagent' pointing to the OpenTelemetry agent, and check if JDBC-based database connections are being used. Look for OpenTelemetry logs or tracing output showing JDBC instrumentation loaded.
    Affected if The agent is attached and JDBC connections are being instrumented (SQL statements appear in traces)
  4. Inspect exported trace data for credential exposure
    Examine your observability backend (Jaeger, Zipkin, OTLP receiver) for recent traces containing SQL CONNECT statements. Search for span attributes containing database connection strings with passwords visible in plain text.
    Affected if Traces contain SQL statements or connection attributes with unmasked passwords that were exported to your observability backend

Your environment is affected if you use OpenTelemetry Java Instrumentation version below 2.28.0 with JDBC auto-instrumentation enabled, and your exported traces contain unredacted database passwords in SQL CONNECT statements.

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 2.28.0 or later
Fixed in 2.28.0
Interim mitigation

Upgrade OpenTelemetry Java Instrumentation to version 2.28.0 or later to patch the password sanitization failure in JDBC auto-instrumentation.

Recommended fix High confidence

2.28.0

  1. 1. Locate the OpenTelemetry Java Instrumentation dependency in your project's build configuration (e.g., pom.xml, build.gradle)
  2. 2. Update the opentelemetry-java-instrumentation dependency version to 2.28.0 or later
  3. 3. Rebuild your application to incorporate the updated dependency
  4. 4. Verify that JDBC connections still function correctly after the upgrade
  5. 5. Test that SQL CONNECT statements with double-quoted passwords are now properly sanitized and not exposed in trace attributes
  6. 6. Confirm that your observability backend is not receiving password data in span attributes
Caveat Review the OpenTelemetry Java Instrumentation 2.28.0 release notes for any deprecation notices or behavioral changes that may affect your application

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

Fix this in Opentelemetry Instrumentation For Java Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-54704 — 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-54704 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