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

published 2026-10-02 37 d ago modified 2026-10-06 33 d ago also GHSA-qqmp-wf37-98f9 , EUVD-2026-91788

cvss: 5.8; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.2%; EPSS 0.2% chance of exploitation in 30 days, percentile 15%
public exploits: 0; none known

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.

Patch / fix

fixed in 8 links 3

npm @opentelemetry/instrumentation-cassandra-driver 0.66.0
npm @opentelemetry/instrumentation-tedious 0.40.0
npm @opentelemetry/instrumentation-oracledb 0.46.0
npm @opentelemetry/instrumentation-mongoose 0.67.0
npm @opentelemetry/instrumentation-mysql 0.67.0
npm @opentelemetry/instrumentation-knex 0.65.0
npm @opentelemetry/instrumentation-mysql2 0.67.0
npm @opentelemetry/instrumentation-pg 0.73.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-104872 updated 2026-10-27 cvss 5.3

@opentelemetry/instrumentation-cassandra-driver: @opentelemetry/instrumentation-knex: @opentelemetry/instrumentation-mongoose: @opentelemetry/instrumentation-mysql: @opentelemetry/instrumentation-mysq

Red Hat Developer Hub 1 rhdh/rhdh-hub-rhel9 Red Hat Self-service automation portal 2 ansible-automation-platform/bootc-automation-portal-rhel9
affected: workaround, no fix available “Update to fixed versions. Workaround: a custom SpanProcessor can be used to strip db.user from spans before export.”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: 33 d ago (2026-10-06)

Exploit prediction

0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	5.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
GitHub	3.1	5.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
npm	@opentelemetry/instrumentation-cassandra-driver	<0.66.0	0.66.0
npm	@opentelemetry/instrumentation-tedious	<0.40.0	0.40.0
npm	@opentelemetry/instrumentation-oracledb	<0.46.0	0.46.0
npm	@opentelemetry/instrumentation-mongoose	<0.67.0	0.67.0
npm	@opentelemetry/instrumentation-mysql	<0.67.0	0.67.0
npm	@opentelemetry/instrumentation-knex	<0.65.0	0.65.0
npm	@opentelemetry/instrumentation-mysql2	<0.67.0	0.67.0
npm	@opentelemetry/instrumentation-pg	<0.73.0	0.73.0

Affected products

open-telemetry opentelemetry-js-contrib
@opentelemetry instrumentation-cassandra-driver
@opentelemetry instrumentation-knex
@opentelemetry instrumentation-mongoose
@opentelemetry instrumentation-mysql
@opentelemetry instrumentation-mysql2
@opentelemetry instrumentation-oracledb
@opentelemetry instrumentation-pg
@opentelemetry instrumentation-tedious

Classification

Weakness

CWE-532 Insertion of Sensitive Information into Log File

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary