Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-104872 medium CVSS 5.8

Vulnerability in @opentelemetry/instrumentation-cassandra-driver (CVE-2026-104872)

Summary

Vulnerability in @opentelemetry/instrumentation-cassandra-driver (CVE-2026-104872). Risk of unauthorized operations or information disclosure. Exploitable via db.user. Mitigation: upgrade to 0.66.0 or later.

Original description

The description as published by the source.

Impact

Multiple @opentelemetry/instrumentation-* packages recorded the database connection username as the db.user
span attribute on every instrumented database operation. This attribute was emitted unconditionally — it was
not gated by enhancedDatabaseReporting or any other opt-in flag, and it was the default behaviour for
all users of the affected packages until the patched releases shipped on 2026-07-23.

The attribute is forwarded to every configured observability backend (Jaeger, Zipkin, Datadog, OTLP
collectors, etc.). Depending on the database account naming convention in use, the exported value may
reveal:

  • Internal service account names that disclose architecture topology.
  • Role-encoded usernames (e.g. admin_readwrite, app_readonly_prod) useful for privilege inference.
  • Database account naming patterns useful for credential enumeration.

Affected packages (all are vulnerable from the first published version through the version listed below):

Package Vulnerable range Patched version
@opentelemetry/instrumentation-cassandra-driver < 0.66.0 0.66.0
@opentelemetry/instrumentation-knex < 0.65.0 0.65.0
@opentelemetry/instrumentation-mongoose < 0.67.0 0.67.0
@opentelemetry/instrumentation-mysql < 0.67.0 0.67.0
@opentelemetry/instrumentation-mysql2 < 0.67.0 0.67.0
`@opentelemetry/instr…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-104872 has been found in @opentelemetry/instrumentation-cassandra-driver.
Attackers can target a specific entry point like db.user over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.8/10.
What to do: upgrade @opentelemetry/instrumentation-cassandra-driver to 0.66.0 or later.
If unsure, ask your IT team or search "@opentelemetry/instrumentation-cassandra-driver CVE-2026-104872" on the vendor's site.

CVE-2026-104872 (@opentelemetry/instrumentation-cassandra-driver) — CWE-532 / CVSS v3 5.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: db.user / enhancedDatabaseReporting / admin_readwrite / app_readonly_prod
Patched: 0.66.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-532) exists in @opentelemetry/instrumentation-cassandra-driver. Attackers reach the vulnerable code path via db.user without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of @opentelemetry/instrumentation-cassandra-driver. Attack surface: db.user / enhancedDatabaseReporting / admin_readwrite / app_readonly_prod.

🔥 Severity

Severity: Medium (CVSS 5.8/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.66.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@opentelemetry/instrumentation-cassandra-driver' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r '@opentelemetry/instrumentation-cassandra-driver' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @opentelemetry/instrumentation-cassandra-driver を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade @opentelemetry/instrumentation-cassandra-driver to 0.66.0

    ステージング環境で 0.66.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @opentelemetry/instrumentation-cassandra-driver
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.66.0"}]}]
npm @opentelemetry/instrumentation-tedious
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.40.0"}]}]
npm @opentelemetry/instrumentation-oracledb
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.46.0"}]}]
npm @opentelemetry/instrumentation-mongoose
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.67.0"}]}]
npm @opentelemetry/instrumentation-mysql
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.67.0"}]}]
npm @opentelemetry/instrumentation-knex
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.65.0"}]}]
npm @opentelemetry/instrumentation-mysql2
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.67.0"}]}]
npm @opentelemetry/instrumentation-pg
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.73.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details