{"answers":{"affected":"2 open source packages ship an affected version, including io.opentelemetry.javaagent:opentelemetry-javaagent. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-54704 in the wild and no public exploit code.","fix":"Upgrade io.opentelemetry.javaagent:opentelemetry-javaagent to 2.28.0-alpha or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-54704 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-54704 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- io.opentelemetry.javaagent:opentelemetry-javaagent (Maven): affected all versions; fixed in 2.28.0-alpha\n- io.opentelemetry.javaagent:opentelemetry-javaagent (Maven): affected all versions; fixed in 2.28.0-alpha\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54704/ (Markdown: https://insights.sbomify.com/CVE-2026-54704/index.md)","id":"CVE-2026-54704","markdown":"https://insights.sbomify.com/CVE-2026-54704/index.md","name":"CVE-2026-54704","record":{"aliases":["GHSA-rwqx-fvqh-6wm4"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Java instrumentation library","requires_auth":"low_privilege","summary":"Attackers with access to observability backends can read clear-text database passwords leaked via unsanitized JDBC trace attributes.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"opentelemetry_instrumentation_for_java","vendor":"linuxfoundation"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"OpenTelemetry Java Instrumentation: JDBC Auto-Instrumentation Logging Clear-Text Passwords","id":"CVE-2026-54704","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"mathlive's Lack of Escaping of HTML allows for XSS","id":"CVE-2026-54705"},"packages":[{"ecosystem":"Maven","fixed":["2.28.0-alpha"],"introduced":["0"],"last_affected":[],"package":"io.opentelemetry.javaagent:opentelemetry-javaagent","purl":null,"source":"GHSA-rwqx-fvqh-6wm4"},{"ecosystem":"Maven","fixed":["2.28.0-alpha"],"introduced":["0"],"last_affected":[],"package":"io.opentelemetry.javaagent:opentelemetry-javaagent","purl":"pkg:maven/io.opentelemetry.javaagent/opentelemetry-javaagent","source":"GHSA-rwqx-fvqh-6wm4"}],"prev":{"headline":"Markdown Preview Enhanced: Arbitrary File Write via updateMarkdown Command Without Path Validation","id":"CVE-2026-54703"},"products":["opentelemetry-java-instrumentation"],"published":"2026-07-01","related":[{"cvss_score":9.3,"headline":"OpenTelemetry: Unsafe Deserialization in RMI Instrumentation may Lead to Remote Code Execution","id":"CVE-2026-33701","kev_date_added":null,"published":"2026-03-27"},{"cvss_score":6.5,"headline":"Information disclosure in opentelemetry-java-instrumentation","id":"CVE-2023-39951","kev_date_added":null,"published":"2023-08-08"},{"cvss_score":5.3,"headline":"OpenTelemetry Javaagent RMI context propagation allows resource exhaustion","id":"CVE-2026-54712","kev_date_added":null,"published":"2026-07-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-02","vendors":["open-telemetry"]},"summary":"Attackers with access to observability backends can read clear-text database passwords leaked via unsanitized JDBC trace attributes.","url":"https://insights.sbomify.com/CVE-2026-54704/"}