NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

OpenTelemetry Java Instrumentation: JDBC Auto-Instrumentation Logging Clear-Text PasswordsGHSA-rwqx-fvqh-6wm4

MEDIUMFix: open-telemetry/opentelemetry-java-instrumentation#18754

GHSA-rwqx-fvqh-6wm4 is a medium-severity (CVSS 6.5) CWE-532 vulnerability in io.opentelemetry.javaagent:opentelemetry-javaagent. A fix is available for io.opentelemetry.javaagent:opentelemetry-javaagent — see the affected versions and patch details below.

Also known asCVE-2026-54704
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 30, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-rwqx-fvqh-6wm4.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs32th percentile — riskier than 32% of all scored CVEsHighest risk
0.00%0.29%0.59%0.88%0.2%0.4%0.4%0.4%Aug 26Oct 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
☕io.opentelemetry.javaagent:opentelemetry-javaagent

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenio.opentelemetry.javaagent:opentelemetry-javaagentall versions2.28.0-alphaio.opentelemetry.javaagent:opentelemetry-javaagent:2.28.0-alpha

Affected Products

1 product · 1 configurations
Application
opentelemetry instrumentation for javalinuxfoundation
< 2.28.0
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.opentelemetry.javaagent:opentelemetry-javaagent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update io.opentelemetry.javaagent:opentelemetry-javaagent to 2.28.0-alpha or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rwqx-fvqh-6wm4 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-rwqx-fvqh-6wm4 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
OpenTelemetry Java Instrumentation: JDBC…