Skip to main content
VulnerabilityPublished Updated

CVE-2026-104872: open-telemetry opentelemetry-js-contrib · Sensitive Data in Logs

Affects open-telemetry opentelemetry-js-contribSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.8 Medium · fixed in 0.66.0 : update open-telemetry opentelemetry-js-contrib when convenient.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
5.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.66.0, 0.65.0, 0.67.0 +3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
open-telemetryopentelemetry-js-contribAffected
  • =< 27e172a9e0d549559056ccd58f27d13467454156
Fixed in–
@opentelemetryinstrumentation-cassandra-driverAffected
  • <0.66.0
Fixed in
  • 0.66.0
@opentelemetryinstrumentation-knexAffected
  • <0.65.0
Fixed in
  • 0.65.0
@opentelemetryinstrumentation-mongooseAffected
  • <0.67.0
Fixed in
  • 0.67.0
@opentelemetryinstrumentation-mysqlAffected
  • <0.67.0
Fixed in
  • 0.67.0
@opentelemetryinstrumentation-mysql2Affected
  • <0.67.0
Fixed in
  • 0.67.0

AI-suggested

A fix is available in versions 0.66.0, 0.65.0, 0.67.0, 0.46.0, 0.73.0, and 0.40.0 of the respective OpenTelemetry instrumentation packages. Users should upgrade to these versions or later to prevent the automatic inclusion of database usernames in telemetry data. No additional configuration changes are required once updated.

Description

OpenTelemetry JavaScript Contrib instrumentation libraries prior to specified versions include the database connection username in telemetry data as the db.user span attribute by default. This sensitive information is logged and sent to observability backends without requiring opt-in, potentially exposing service topology, roles, environment details, and account naming patterns. The issue is addressed 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.

References

Community reviews

Loading reviews…