Vulnerability in io.opentelemetry.javaagent:opentelemetry-javaagent (CVE-2026-54704)
Summary
Vulnerability in io.opentelemetry.javaagent:opentelemetry-javaagent (CVE-2026-54704). Confidential information can be exposed externally. Mitigation: upgrade to 2.28.0-alpha or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54704 has been found in io.opentelemetry.javaagent:opentelemetry-javaagent.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade io.opentelemetry.javaagent:opentelemetry-javaagent to 2.28.0-alpha or later.
If unsure, ask your IT team or search "io.opentelemetry.javaagent:opentelemetry-javaagent CVE-2026-54704" on the vendor's site.
CVE-2026-54704 (io.opentelemetry.javaagent:opentelemetry-javaagent) — CWE-532 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.28.0-alpha — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-532) exists in io.opentelemetry.javaagent:opentelemetry-javaagent.
Check the vendor advisory for the affected versions of io.opentelemetry.javaagent:opentelemetry-javaagent.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
Update to 2.28.0-alpha.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで io.opentelemetry.javaagent:opentelemetry-javaagent を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade io.opentelemetry.javaagent:opentelemetry-javaagent to 2.28.0-alphaステージング環境で 2.28.0-alpha に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com