# CVE-2026-54704: OpenTelemetry Java Instrumentation: JDBC Auto-Instrumentation Logging Clear-Text Passwords

> Attackers with access to observability backends can read clear-text database passwords leaked via unsanitized JDBC trace attributes.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Jul 2026
- **Updated:** 2 Jul 2026
- **Also known as:** GHSA-rwqx-fvqh-6wm4

## What is CVE-2026-54704?

CVE-2026-54704 is a medium-severity vulnerability in open-telemetry opentelemetry-java-instrumentation, published on 1 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2026-54704?

2 open source packages ship an affected version, including io.opentelemetry.javaagent:opentelemetry-javaagent. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.opentelemetry.javaagent:opentelemetry-javaagent` | Maven | All versions | 2.28.0-alpha |
| `io.opentelemetry.javaagent:opentelemetry-javaagent` | Maven | All versions | 2.28.0-alpha |

Products: Linuxfoundation Opentelemetry Instrumentation for Java.

## How do I fix CVE-2026-54704?

Upgrade io.opentelemetry.javaagent:opentelemetry-javaagent to 2.28.0-alpha or later.

## Is CVE-2026-54704 being exploited?

There is no known exploitation of CVE-2026-54704 in the wild and no public exploit code.

## Other vulnerabilities in open-telemetry opentelemetry-java-instrumentation

- [CVE-2026-33701](https://insights.sbomify.com/CVE-2026-33701/): OpenTelemetry: Unsafe Deserialization in RMI Instrumentation may Lead to Remote Code Execution (critical 9.3)
- [CVE-2023-39951](https://insights.sbomify.com/CVE-2023-39951/): Information disclosure in opentelemetry-java-instrumentation (medium 6.5)
- [CVE-2026-54712](https://insights.sbomify.com/CVE-2026-54712/): OpenTelemetry Javaagent RMI context propagation allows resource exhaustion (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54704 and fix it if it is affected.

What it is: CVE-2026-54704 is a medium-severity vulnerability in open-telemetry opentelemetry-java-instrumentation, published on 1 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54704 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.opentelemetry.javaagent:opentelemetry-javaagent (Maven): affected all versions; fixed in 2.28.0-alpha
- io.opentelemetry.javaagent:opentelemetry-javaagent (Maven): affected all versions; fixed in 2.28.0-alpha

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54704/ (Markdown: https://insights.sbomify.com/CVE-2026-54704/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54704
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54704
- OSV: https://osv.dev/vulnerability/CVE-2026-54704

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54704/
Summaries are generated and may contain mistakes; the official description above is the record.