CVSS 3.1
5.8 mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:NMedium (5.8). EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in @opentelemetry/instrumentation-cassandra-driver 0.66.0.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N@opentelemetry/instrumentation-cassandra-driver (npm): fixed in 0.66.0@opentelemetry/instrumentation-tedious (npm): fixed in 0.40.0@opentelemetry/instrumentation-oracledb (npm): fixed in 0.46.0@opentelemetry/instrumentation-mongoose (npm): fixed in 0.67.0@opentelemetry/instrumentation-mysql (npm): fixed in 0.67.0@opentelemetry/instrumentation-knex (npm): fixed in 0.65.0@opentelemetry/instrumentation-mysql2 (npm): fixed in 0.67.0@opentelemetry/instrumentation-pg (npm): fixed in 0.73.0Explain CVE-2026-104872 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-104872?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-104872?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-104872 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| open-telemetry opentelemetry-js-contrib | < 27e172a9e0d549559056ccd58f27d13467454156 |
| @opentelemetry instrumentation-cassandra-driver | < 0.66.0 |
| @opentelemetry instrumentation-knex | < 0.65.0 |
| @opentelemetry instrumentation-mongoose | < 0.67.0 |
| @opentelemetry instrumentation-mysql | < 0.67.0 |
| @opentelemetry instrumentation-mysql2 | < 0.67.0 |
| @opentelemetry instrumentation-oracledb | < 0.46.0 |
| @opentelemetry instrumentation-pg | < 0.73.0 |
| @opentelemetry instrumentation-tedious | < 0.40.0 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-qqmp-wf37-98f9 | npm | @opentelemetry/instrumentation-cassandra-driver | <0.66.0 | 0.66.0 |
| GHSA-qqmp-wf37-98f9 | npm | @opentelemetry/instrumentation-tedious | <0.40.0 | 0.40.0 |
| GHSA-qqmp-wf37-98f9 | npm | @opentelemetry/instrumentation-oracledb | <0.46.0 | 0.46.0 |
| GHSA-qqmp-wf37-98f9 | npm | @opentelemetry/instrumentation-mongoose | <0.67.0 | 0.67.0 |
| GHSA-qqmp-wf37-98f9 | npm | @opentelemetry/instrumentation-mysql | <0.67.0 | 0.67.0 |
| GHSA-qqmp-wf37-98f9 | npm | @opentelemetry/instrumentation-knex | <0.65.0 | 0.65.0 |
| GHSA-qqmp-wf37-98f9 | npm | @opentelemetry/instrumentation-mysql2 | <0.67.0 | 0.67.0 |
| GHSA-qqmp-wf37-98f9 | npm | @opentelemetry/instrumentation-pg | <0.73.0 | 0.73.0 |
Red Hat rates this Moderate.
Some `@opentelemetry/instrumentation-*` packages unconditionally emitted the db.user span attribute (database connection username) on every instrumented database operation. This was default behaviour, not gated by any opt-in flag. The username is forwarded to all configured observability backends (Jaeger, Zipkin, Datadog, OTLP collectors), potentially revealing service account names, role-encoded usernames, and architecture topology.
Only usernames are leaked — no passwords, connection strings, or data.
Update to fixed versions.
Workaround: a custom SpanProcessor can be used to strip db.user from spans before export.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Developer Hub 1 | rhdh/rhdh-hub-rhel9 | Fix deferred | |
| Self-service automation portal 2 | ansible-automation-platform/bootc-automation-portal-rhel9 | Fix deferred |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-104872.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.