Is CVE-2026-104872 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-104872 being exploited in the wild.

How severe is CVE-2026-104872?

Medium severity, with a CVSS score of 5.8, published 2 October 2026.

Which products and versions are affected?

@opentelemetry/instrumentation-cassandra-driver (npm) < 0.66.0, SEMVER:introduced=0,fixed=0.66.0; @opentelemetry/instrumentation-knex (npm) < 0.65.0, SEMVER:introduced=0,fixed=0.65.0; @opentelemetry/instrumentation-mongoose (npm) < 0.67.0, SEMVER:introduced=0,fixed=0.67.0; @opentelemetry/instrumentation-mysql (npm) < 0.67.0, SEMVER:introduced=0,fixed=0.67.0; and 12 more.

Is there a fix for CVE-2026-104872?

Yes. @opentelemetry/instrumentation-cassandra-driver (npm): upgrade to 0.66.0 or later; @opentelemetry/instrumentation-knex (npm): upgrade to 0.65.0 or later; @opentelemetry/instrumentation-mongoose (npm): upgrade to 0.67.0 or later; @opentelemetry/instrumentation-mysql (npm): upgrade to 0.67.0 or later; @opentelemetry/instrumentation-mysql2 (npm): upgrade to 0.67.0 or later; @opentelemetry/instrumentation-oracledb (npm): upgrade to 0.46.0 or later; @opentelemetry/instrumentation-pg (npm): upgrade to 0.73.0 or later; @opentelemetry/instrumentation-tedious (npm): upgrade to 0.40.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-104872 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-104872?

Check whether you run @opentelemetry/instrumentation-cassandra-driver (npm), @opentelemetry/instrumentation-knex (npm), @opentelemetry/instrumentation-mongoose (npm) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-104872: OpenTelemetry JavaScript Contrib database credentials exposure in span attributes

Q: Is there a fix for CVE-2026-104872?

Yes. @opentelemetry/instrumentation-cassandra-driver (npm): upgrade to 0.66.0 or later; @opentelemetry/instrumentation-knex (npm): upgrade to 0.65.0 or later; @opentelemetry/instrumentation-mongoose (npm): upgrade to 0.67.0 or later; @opentelemetry/instrumentation-mysql (npm): upgrade to 0.67.0 or later; @opentelemetry/instrumentation-mysql2 (npm): upgrade to 0.67.0 or later; @opentelemetry/instrumentation-oracledb (npm): upgrade to 0.46.0 or later; @opentelemetry/instrumentation-pg (npm): upgrade to 0.73.0 or later; @opentelemetry/instrumentation-tedious (npm): upgrade to 0.40.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-104872 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-104872?

Check whether you run @opentelemetry/instrumentation-cassandra-driver (npm), @opentelemetry/instrumentation-knex (npm), @opentelemetry/instrumentation-mongoose (npm) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-104872 · Severity: medium · CVSS 5.8 · Published 2026-10-02

OpenTelemetry JavaScript Contrib provides instrumentation libraries that automatically capture telemetry data from database operations. These libraries were emitting database connection usernames as span attributes sent to observability backends by default, exposing account credentials and potentially revealing service topology and environment information to anyone with access to telemetry data.

Vendors: npm, Opentelemetry.

Quick answers

Is CVE-2026-104872 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-104872 being exploited in the wild.
How severe is CVE-2026-104872?: Medium severity, with a CVSS score of 5.8, published 2 October 2026.
Which products and versions are affected?: @opentelemetry/instrumentation-cassandra-driver (npm) < 0.66.0, SEMVER:introduced=0,fixed=0.66.0; @opentelemetry/instrumentation-knex (npm) < 0.65.0, SEMVER:introduced=0,fixed=0.65.0; @opentelemetry/instrumentation-mongoose (npm) < 0.67.0, SEMVER:introduced=0,fixed=0.67.0; @opentelemetry/instrumentation-mysql (npm) < 0.67.0, SEMVER:introduced=0,fixed=0.67.0; and 12 more.
Is there a fix for CVE-2026-104872?: Yes. @opentelemetry/instrumentation-cassandra-driver (npm): upgrade to 0.66.0 or later; @opentelemetry/instrumentation-knex (npm): upgrade to 0.65.0 or later; @opentelemetry/instrumentation-mongoose (npm): upgrade to 0.67.0 or later; @opentelemetry/instrumentation-mysql (npm): upgrade to 0.67.0 or later; @opentelemetry/instrumentation-mysql2 (npm): upgrade to 0.67.0 or later; @opentelemetry/instrumentation-oracledb (npm): upgrade to 0.46.0 or later; @opentelemetry/instrumentation-pg (npm): upgrade to 0.73.0 or later; @opentelemetry/instrumentation-tedious (npm): upgrade to 0.40.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-104872 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-104872?: Check whether you run @opentelemetry/instrumentation-cassandra-driver (npm), @opentelemetry/instrumentation-knex (npm), @opentelemetry/instrumentation-mongoose (npm) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@opentelemetry/instrumentation-cassandra-driver (npm): upgrade to 0.66.0 or later
```
npm install @opentelemetry/instrumentation-cassandra-driver@0.66.0
```
@opentelemetry/instrumentation-knex (npm): upgrade to 0.65.0 or later
```
npm install @opentelemetry/instrumentation-knex@0.65.0
```
@opentelemetry/instrumentation-mongoose (npm): upgrade to 0.67.0 or later
```
npm install @opentelemetry/instrumentation-mongoose@0.67.0
```
@opentelemetry/instrumentation-mysql (npm): upgrade to 0.67.0 or later
```
npm install @opentelemetry/instrumentation-mysql@0.67.0
```
@opentelemetry/instrumentation-mysql2 (npm): upgrade to 0.67.0 or later
```
npm install @opentelemetry/instrumentation-mysql2@0.67.0
```
@opentelemetry/instrumentation-oracledb (npm): upgrade to 0.46.0 or later
```
npm install @opentelemetry/instrumentation-oracledb@0.46.0
```
@opentelemetry/instrumentation-pg (npm): upgrade to 0.73.0 or later
```
npm install @opentelemetry/instrumentation-pg@0.73.0
```
@opentelemetry/instrumentation-tedious (npm): upgrade to 0.40.0 or later
```
npm install @opentelemetry/instrumentation-tedious@0.40.0
```

Technical details

Multiple OpenTelemetry instrumentation packages for database drivers (Cassandra, Knex, Mongoose, MySQL, MySQL2, OracleDB, PostgreSQL, and SQL Server) added database connection usernames to span attributes by default without an opt-in control, exposing credentials to configured observability backends. The vulnerability is an information disclosure issue affecting database instrumentation layers that emit telemetry by default to external systems.

Affected products

OpenTelemetry instrumentation-cassandra-driver prior to 0.66.0
OpenTelemetry instrumentation-knex prior to 0.65.0
OpenTelemetry instrumentation-mongoose prior to 0.67.0
OpenTelemetry instrumentation-mysql prior to 0.67.0
OpenTelemetry instrumentation-mysql2 prior to 0.67.0
OpenTelemetry instrumentation-oracledb prior to 0.46.0
OpenTelemetry instrumentation-pg prior to 0.73.0
OpenTelemetry instrumentation-tedious prior to 0.40.0

Identifiers

CVE-2026-104872
GHSA-qqmp-wf37-98f9

Timeline

2026-10-02: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.