# CVE-2026-104872: Multiple @opentelemetry/instrumentation-* packages expose database username via unconditional db.user span attribute > OpenTelemetry instrumentation libraries leak database usernames in span attributes by default, exposing sensitive account information to observability backends. - **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 2 Oct 2026 - **Updated:** 6 Oct 2026 - **Also known as:** ECHO-980f-e1f1-2a12, GHSA-qqmp-wf37-98f9, MINI-2v4g-5fjf-cwfc, MINI-4x6f-6fv6-5pw8, MINI-5532-3695-jhqr, MINI-722w-68j5-9jpr, MINI-96gv-3vqj-j2mp, MINI-mcvg-mx93-7qq4, MINI-mvj5-9gjj-qffg, MINI-ph7x-w8hw-jv4f, MINI-xj5v-4jm4-4c8p ## What is CVE-2026-104872? CVE-2026-104872 is a medium-severity vulnerability in @opentelemetry instrumentation-cassandra-driver, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description OpenTelemetry JavaScript Contrib provides instrumentation libraries for collecting telemetry from JavaScript applications. Prior to versions 0.66.0 of @opentelemetry/instrumentation-cassandra-driver, 0.65.0 of @opentelemetry/instrumentation-knex, 0.67.0 of @opentelemetry/instrumentation-mongoose, @opentelemetry/instrumentation-mysql, and @opentelemetry/instrumentation-mysql2, 0.46.0 of @opentelemetry/instrumentation-oracledb, 0.73.0 of @opentelemetry/instrumentation-pg, and 0.40.0 of @opentelemetry/instrumentation-tedious, the packages add the database connection username to every instrumented database operation as the db.user span attribute. The attribute is emitted by default and is not controlled by enhancedDatabaseReporting or another opt-in setting. Configured observability backends therefore receive database account names that may expose service topology, role or environment information, and account naming patterns. This issue is fixed in versions 0.66.0, 0.65.0, 0.67.0, 0.46.0, 0.73.0, and 0.40.0 of the respective packages. Weakness: CWE-532 (Insertion of Sensitive Information into Log File) ## Which versions are affected by CVE-2026-104872? 16 open source packages ship an affected version, including @opentelemetry/instrumentation-cassandra-driver, @opentelemetry/instrumentation-knex and @opentelemetry/instrumentation-mongoose. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `@opentelemetry/instrumentation-cassandra-driver` | npm | All versions | 0.66.0 | | `@opentelemetry/instrumentation-cassandra-driver` | npm | All versions | 0.66.0 | | `@opentelemetry/instrumentation-knex` | npm | All versions | 0.65.0 | | `@opentelemetry/instrumentation-knex` | npm | All versions | 0.65.0 | | `@opentelemetry/instrumentation-mongoose` | npm | All versions | 0.67.0 | | `@opentelemetry/instrumentation-mongoose` | npm | All versions | 0.67.0 | | `@opentelemetry/instrumentation-mysql` | npm | All versions | 0.67.0 | | `@opentelemetry/instrumentation-mysql` | npm | All versions | 0.67.0 | | `@opentelemetry/instrumentation-mysql2` | npm | All versions | 0.67.0 | | `@opentelemetry/instrumentation-mysql2` | npm | All versions | 0.67.0 | | `@opentelemetry/instrumentation-oracledb` | npm | All versions | 0.46.0 | | `@opentelemetry/instrumentation-oracledb` | npm | All versions | 0.46.0 | | `@opentelemetry/instrumentation-pg` | npm | All versions | 0.73.0 | | `@opentelemetry/instrumentation-pg` | npm | All versions | 0.73.0 | | `@opentelemetry/instrumentation-tedious` | npm | All versions | 0.40.0 | | `@opentelemetry/instrumentation-tedious` | npm | All versions | 0.40.0 | ## How do I fix CVE-2026-104872? Upgrade @opentelemetry/instrumentation-cassandra-driver to 0.66.0 or later. ## Is CVE-2026-104872 being exploited? There is no known exploitation of CVE-2026-104872 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-104872 and fix it if it is affected. What it is: CVE-2026-104872 is a medium-severity vulnerability in @opentelemetry instrumentation-cassandra-driver, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-104872 in the wild and no public exploit code. Affected packages and fixed versions: - @opentelemetry/instrumentation-cassandra-driver (npm): affected all versions; fixed in 0.66.0 - @opentelemetry/instrumentation-cassandra-driver (npm): affected all versions; fixed in 0.66.0 - @opentelemetry/instrumentation-knex (npm): affected all versions; fixed in 0.65.0 - @opentelemetry/instrumentation-knex (npm): affected all versions; fixed in 0.65.0 - @opentelemetry/instrumentation-mongoose (npm): affected all versions; fixed in 0.67.0 - @opentelemetry/instrumentation-mongoose (npm): affected all versions; fixed in 0.67.0 - @opentelemetry/instrumentation-mysql (npm): affected all versions; fixed in 0.67.0 - @opentelemetry/instrumentation-mysql (npm): affected all versions; fixed in 0.67.0 - @opentelemetry/instrumentation-mysql2 (npm): affected all versions; fixed in 0.67.0 - @opentelemetry/instrumentation-mysql2 (npm): affected all versions; fixed in 0.67.0 - @opentelemetry/instrumentation-oracledb (npm): affected all versions; fixed in 0.46.0 - @opentelemetry/instrumentation-oracledb (npm): affected all versions; fixed in 0.46.0 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-104872/ (Markdown: https://insights.sbomify.com/CVE-2026-104872/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-104872 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-104872 - OSV: https://osv.dev/vulnerability/CVE-2026-104872 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-104872/ Summaries are generated and may contain mistakes; the official description above is the record.