NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2026-104872: Multiple @opentelemetry/instrumentation-* packages expose database username via unconditional db.user span attribute

mediumCVSS 3.1 5.8GHSA-qqmp-wf37-98f9

Impact Multiple @opentelemetry/instrumentation- packages recorded the database connection username as the db.user span attribute on every instrumented database operation. This attribute was emitted unconditionally — it was not gated by enhancedDatabaseReporting or any other opt-in flag, and it was the default behaviour for all users of the affected packages until the patched releases shipped on 2026-07-23.

Published Oct 5, 2026

Affected packages

@opentelemetry/instrumentation-cassandra-driver

Ecosystem
npm
Affected
< 0.66.0
Fixed in
0.66.0
Check
npm ls @opentelemetry/instrumentation-cassandra-driver

@opentelemetry/instrumentation-tedious

Ecosystem
npm
Affected
< 0.40.0
Fixed in
0.40.0
Check
npm ls @opentelemetry/instrumentation-tedious

@opentelemetry/instrumentation-oracledb

Ecosystem
npm
Affected
< 0.46.0
Fixed in
0.46.0
Check
npm ls @opentelemetry/instrumentation-oracledb

@opentelemetry/instrumentation-mongoose

Ecosystem
npm
Affected
< 0.67.0
Fixed in
0.67.0
Check
npm ls @opentelemetry/instrumentation-mongoose

@opentelemetry/instrumentation-mysql

Ecosystem
npm
Affected
< 0.67.0
Fixed in
0.67.0
Check
npm ls @opentelemetry/instrumentation-mysql

@opentelemetry/instrumentation-knex

Ecosystem
npm
Affected
< 0.65.0
Fixed in
0.65.0
Check
npm ls @opentelemetry/instrumentation-knex

@opentelemetry/instrumentation-mysql2

Ecosystem
npm
Affected
< 0.67.0
Fixed in
0.67.0
Check
npm ls @opentelemetry/instrumentation-mysql2

@opentelemetry/instrumentation-pg

Ecosystem
npm
Affected
< 0.73.0
Fixed in
0.73.0
Check
npm ls @opentelemetry/instrumentation-pg

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Impact

Multiple @opentelemetry/instrumentation-* packages recorded the database connection username as the db.user span attribute on every instrumented database operation. This attribute was emitted unconditionally — it was not gated by enhancedDatabaseReporting or any other opt-in flag, and it was the default behaviour for all users of the affected packages until the patched releases shipped on 2026-07-23.

The attribute is forwarded to every configured observability backend (Jaeger, Zipkin, Datadog, OTLP collectors, etc.). Depending on the database account naming convention in use, the exported value may reveal:

  • Internal service account names that disclose architecture topology.
  • Role-encoded usernames (e.g. admin_readwrite, app_readonly_prod) useful for privilege inference.
  • Database account naming patterns useful for credential enumeration.

Affected packages (all are vulnerable from the first published version through the version listed below):

| Package | Vulnerable range | Patched version |
| `@opentelemetry/instrumentation-cassandra-driver` | `< 0.66.0` | `0.66.0` |
| `@opentelemetry/instrumentation-knex`             | `< 0.65.0` | `0.65.0` |
| `@opentelemetry/instrumentation-mongoose`         | `< 0.67.0` | `0.67.0` |
| `@opentelemetry/instrumentation-mysql`            | `< 0.67.0` | `0.67.0` |
| `@opentelemetry/instrumentation-mysql2`           | `< 0.67.0` | `0.67.0` |
| `@opentelemetry/instrumentation-oracledb`         | `< 0.46.0` | `0.46.0` |
| `@opentelemetry/instrumentation-pg`               | `< 0.73.0` | `0.73.0` |
| `@opentelemetry/instrumentation-tedious`          | `< 0.40.0` | `0.40.0` |

Patches

Fixed in the coordinated release on 2026-07-23 via feat!: only emit stable http, network and database attributes (#3585).

Upgrade to the patched version listed in the table above for each instrumentation package in use.

Workarounds

No configuration-level workaround exists in the affected versions: the db.user attribute cannot be suppressed without patching. As a partial mitigation, a custom SpanProcessor can be used to strip db.user from spans before they leave the process:

// Example: drop db.user in a custom SpanProcessor
class StripDbUserProcessor implements SpanProcessor {
  onStart(span: Span) {
    span.setAttribute('db.user', null);
  }
  onEnd() {}
  shutdown() { return Promise.resolve(); }
  forceFlush() { return Promise.resolve(); }
}

Users who control the downstream collector can also filter the attribute at the collector pipeline level.

Credited to 18kiran08, maryliag, pichlermarc.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology