Skip to content
VulniPulse
Advisory severityMedium5.3Red Hat Linux Updated

Medium [CVE-2026-104872] @opentelemetry/instrumentation-cassandra-driver: @opentelemetry/instrumentation-knex: @opentelemetry/instrumentation-mongoose: @opentelemetry/instrumentation-mysql: @opentelemetry/instrumentation-m…

This medium-severity Red Hat Linux advisory covers CVE-2026-104872; related products: Red Hat Developer Hub, Self-service automation portal 2.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-104872 Source published Source updated

VulniPulse record published Record updated

Related products & platforms
Red Hat LinuxUnclassified
Open source advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

@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: opentelemetry-js-contrib: Information disclosure via default database username emission in telemetry data.

Red Hat rates this moderate (CVSS 5.3). Weakness: CWE-201.

Affected products named by the advisory: Red Hat Developer Hub; Self-service automation portal 2.

Affected versions
  • < 0.66.0
  • < 0.65.0
  • < 0.67.0
  • < 0.46.0
  • < 0.73.0
  • < 0.40.0

Official advisory · high-confidence parse· fetched 14 hours ago·verify at source

Fixed versions
  • 0.66.0
  • 0.65.0
  • 0.67.0
  • 0.46.0
  • 0.73.0
  • 0.40.0

Official advisory · high-confidence parse· fetched 14 hours ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Update to fixed versions. Workaround: a custom SpanProcessor can be used to strip db.user from spans before export.

Official advisory · high-confidence parse· fetched 14 hours ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.