cve.bz

CVE-2026-104872

5.8 mediumEPSS 0.2%Fix available

Medium (5.8). EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in @opentelemetry/instrumentation-cassandra-driver 0.66.0.

On this page
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.

Severity

CVSS 3.1

5.8 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-532 Insertion of Sensitive Information into Log File
OWASP Top 10
A09:2025 Logging & Alerting Failures
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • @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.0

Ask an AI about this CVE

Show the promptExplain 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.

Affected

  • @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
  • open-telemetry:opentelemetry-js-contrib

Versions

From the CNA's record in the CVE List.

ProductAffected
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

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-qqmp-wf37-98f9npm@opentelemetry/instrumentation-cassandra-driver<0.66.00.66.0
GHSA-qqmp-wf37-98f9npm@opentelemetry/instrumentation-tedious<0.40.00.40.0
GHSA-qqmp-wf37-98f9npm@opentelemetry/instrumentation-oracledb<0.46.00.46.0
GHSA-qqmp-wf37-98f9npm@opentelemetry/instrumentation-mongoose<0.67.00.67.0
GHSA-qqmp-wf37-98f9npm@opentelemetry/instrumentation-mysql<0.67.00.67.0
GHSA-qqmp-wf37-98f9npm@opentelemetry/instrumentation-knex<0.65.00.65.0
GHSA-qqmp-wf37-98f9npm@opentelemetry/instrumentation-mysql2<0.67.00.67.0
GHSA-qqmp-wf37-98f9npm@opentelemetry/instrumentation-pg<0.73.00.73.0

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

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.

Red Hat's mitigation

Update to fixed versions.

Workaround: a custom SpanProcessor can be used to strip db.user from spans before export.

ProductPackageStateAdvisory
Red Hat Developer Hub 1rhdh/rhdh-hub-rhel9Fix deferred
Self-service automation portal 2ansible-automation-platform/bootc-automation-portal-rhel9Fix 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.

Attack patterns (CAPEC)

  • CAPEC-215 Fuzzing for application mapping Likelihood: High · Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON