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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

EPSS

• CVE-2026-104872: 0.24% estimated exploitation activity in the next 30 days; percentile 15.75 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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. adminreadwrite, appreadonlyprod) 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 |…

Published by the source

5 Oct 2026, 22:52 UTC

Last modified by the source

5 Oct 2026, 23:00 UTC

Source last checked

26 Oct 2026, 13:06 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-qqmp-wf37-98f9

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-qqmp-wf37-98f9

3. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-qqmp-wf37-98f9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-104872

Advisory: Multiple @opentelemetry/instrumentation-* packages expose database username via unconditional db.user span attribute
IDs: CVE-2026-104872, GHSA-qqmp-wf37-98f9
Record: https://patchnext.com/advisories/cve-2026-104872 (revision 3, source checked 26 Oct 2026, 13:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @opentelemetry/instrumentation-pg 0.73.0; @opentelemetry/instrumentation-mysql 0.67.0; @opentelemetry/instrumentation-knex 0.65.0; @opentelemetry/instrumentation-mongoose 0.67.0; @opentelemetry/instrumentation-oracledb 0.46.0; @opentelemetry/instrumentation-mysql2 0.67.0; @opentelemetry/instrumentation-tedious 0.40.0; @opentelemetry/instrumentation-cassandra-driver 0.66.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @opentelemetry/instrumentation-pg: affected < 0.73.0; fixed in 0.73.0
- npm @opentelemetry/instrumentation-mysql: affected < 0.67.0; fixed in 0.67.0
- npm @opentelemetry/instrumentation-knex: affected < 0.65.0; fixed in 0.65.0
- npm @opentelemetry/instrumentation-mongoose: affected < 0.67.0; fixed in 0.67.0
- npm @opentelemetry/instrumentation-oracledb: affected < 0.46.0; fixed in 0.46.0
- npm @opentelemetry/instrumentation-mysql2: affected < 0.67.0; fixed in 0.67.0
- npm @opentelemetry/instrumentation-tedious: affected < 0.40.0; fixed in 0.40.0
- npm @opentelemetry/instrumentation-cassandra-driver: affected < 0.66.0; fixed in 0.66.0

## Suggested inspection (read-only)
- `npm ls @opentelemetry/instrumentation-pg --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @opentelemetry/instrumentation-mysql --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @opentelemetry/instrumentation-knex --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @opentelemetry/instrumentation-mongoose --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @opentelemetry/instrumentation-oracledb --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @opentelemetry/instrumentation-mysql2 --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @opentelemetry/instrumentation-tedious --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @opentelemetry/instrumentation-cassandra-driver --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @opentelemetry/instrumentation-pg, @opentelemetry/instrumentation-mysql, @opentelemetry/instrumentation-knex, @opentelemetry/instrumentation-mongoose, @opentelemetry/instrumentation-oracledb, @opentelemetry/instrumentation-mysql2, @opentelemetry/instrumentation-tedious, @opentelemetry/instrumentation-cassandra-driver.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-qqmp-wf37-98f9 (GitHub-reviewed advisory GHSA-qqmp-wf37-98f9 lists affected ranges: npm @opentelemetry/instrumentation-cassandra-driver >=0 =0 =0 =0 =0 =0 =0 <0.67.0; npm…)
- Verified: https://osv.dev/vulnerability/GHSA-qqmp-wf37-98f9 (OSV record GHSA-qqmp-wf37-98f9 lists affected ranges: npm @opentelemetry/instrumentation-cassandra-driver >=0 =0 =0 =0 =0 =0 =0 <0.67.0…)

Commands are suggestions: review each one before running it.